Andreas Saeger wrote:
So we have synonymous groups Numeric/Decimal, Real/Float/Double,
Image/Binary and Other/Object, right? For better readability the table
should merge equivalent types into single lines.
"Binary (fix)" should get a description just like "Text (fix)":
Stores exactly the length specified by user. Pads with trailing null
bytes [??? I don't know] for shorter byte arrays."
Date Stores month, day and year information 1/1/99 to 1/1/9999
I can not enter 2-digit years in a table view. OOo always expands to
4-digit years (1/1/99 --> 1/1/1999) even if entered with leading zeroes.
Right I meant to put 1/1/100 as that seems to be the earliest date I can
get it to take.
Time Stores hour, minute and second info Seconds since 1/1/1970
This is where I get totally confused. I tried to enter some time values
00:00, 24:00 and 48:00. Then I wanted to run a query
SELECT "Time", Cast("Time" AS DATE) AS "Date_Cast" FROM "Times"
in order to see if the dates are 1970-01-01, 1970-01-02 and 1970-01-03
BUT: I can not enter times >=24:00 (truncated to hours 0-23) and cast()
can not convert times to dates. So what is the meaning of "Seconds since
1/1/1970"?
Right again - clear as mud isn't it.
Table "Alphanumeric Types" should be named "String types" since it
doesn't include numerics.
Header "Format" in table "Date time" is confusing since the input format
depends on the office locale whereas the output format depends on the
form control's formatting or table column's formatting respectively.
In table "Numeric types" "Name" refers to the SQL type whereas in the
other tables "Name" refers to the more descriptive name. SQL types
should be written uppercased and without spaces like in the
documentation and the table editor.
Just my 2 €-Cents
Andreas
I agree about the merging synonymous types. The renaming of sections and
columns also.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
