[Harbour] Re: [xHarbour-developers] Extended field types in RDDs
Przemyslaw Czerpak
druzus at acn.waw.pl
Wed Sep 5 02:04:32 EDT 2007
On Tue, 04 Sep 2007, Miguel Angel Marchuet wrote:
> VFP uses the following Array and is possible that sooner or later we also
> need it.
> For that reason I believe that we must to preveer these necessities.
>
> Field info Data type
> 1 Field name Character
> 2 Field type Character
> C = Character
> Y = Currency
> D = Date
> T = DateTime
> B = Double
> F = Float
> G = General
> I = Integer
> L = Logical
> M = Memo
> N = Numeric
> Q = Varbinary
> V = Varchar and Varchar (Binary)
> W = Blob
Can you also send basic size, attributes and usage for these fields?
> 3 Field width Numeric
> 4 Decimal places Numeric
> 5 Null values allowed Logical
> 6 Code page translation not allowed Logical
Is it the same as BINARY flag?
> 7 Field validation expression Character
> 8 Field validation text Character
> 9 Field default value Character
> 10 Table validation expression Character
> 11 Table validation text Character
> 12 Long table name Character
> 13 Insert trigger expression Character
> 14 Update trigger expression Character
> 15 Delete trigger expression Character
> 16 Table comment Character
> 17 NextValue for autoincrementing Numeric
> 18 Step for autoincrementing Numeric
I do not know why 10, 11, 12, 13, 14, 15 and 16 are in column description.
IMHO these are table attributes not columns' ones so they should not be
here. Do you know any reasons why VFP added it here?
> For example i'm thinking about to implement trigers as in SixRDD or similar.
I Implemented SIX3 triggers few years ago for my own use - I can commit
them but like points I'm asking above these are table not columns attributes
so we do not need them in these array but we should create other data holder
for them.
best regards,
Przemek
More information about the Harbour
mailing list