> I think, that the server can do nothing with it. And I do not like > autoincrement columns. Generators/Sequences are much more powerfull. > Only some flag to see the column is generated from generator. But I > have doubts engine will support this.
Why autoincrement fields can't be created with help of generators and special system triggers (as it made for CHECK constraints)? I'm shure this feature already exists in tracker... >> 2) I think that special table will be better solution than comments > Why? Because all will be in one independent place and will be available for editing. > Because view has relations etc. Yes, but this cause similar problem for designer. Each model updating will drop all hand-made changes. > Why somebody would clutter database with this? Why somebody should clutter database with comments? > What about keys on more than one column, etc. etc. etc. Two records with diffirent column names and same table names > And keeping this in sync (and between FB versions - like different length for column names, which is probably going to happen). This is developer's problem. ------------------------------------------------------------------------------ _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
