HP3000-L Archives

August 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Duane Percox <[log in to unmask]>
Reply To:
Duane Percox <[log in to unmask]>
Date:
Sun, 16 Aug 1998 17:05:14 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
>Ken Sletten writes:
>
><snip for brevity>
>
>> LENGTH:
>>
>>   510  bytes for maximum subitem length
>>   4096 bytes for maximum item length
>
>Just a couple of months ago, I tried creating a data base with a
>data set with fields of X256 and DBSCHEMA refused to build the
>root file.  I ended up using two fields of X128 and using them as
>"chunks" of data.  This was on "the latest" version of Image/SQL,
>or at least the version that supports ODBC.   Here is what happens:
>
[dbschema samples with errors snipped...]

Jim - I think these are the current limits as they relate to
      data items:

The largest value for a sub-item length is 255 and the largest value
for sub-item count is 255 (2-255 specifies the item as compound, which
I know you know...).

The size of a single data item (item or compound item) cannot exceed 4094 bytes.

And a data item must size be defined in integral half-words, so the byte
count has to be even (since 1 h/w==2bytes).

Therefore the largest x non compound item you can specify would be x254.


Duane Percox ([log in to unmask]  v/650.372.0200x608 f/650.372.3386)
http://www.qss.com/          http://qwebs.qss.com/qwebs
http://qwebs.qss.com/faq3k

ATOM RSS1 RSS2