>> 1) any column of table or view field (including not primary keys) with >> #PK_GEN# is a key field with autoincrement > > Though it's possible, why would you wanna mark field as PK if it's not > in database? This may (and will, you bet) strange errors.
For views, for very small tables without primari keys, for some cases where NOT NULL UNIQUE KEY should be used instead of PK's. >> 2) any column of table or view field (including not primary keys) with >> #KEY# is a key field without autoincrement > > Similar to 1). Sometimes we can set primary keys manually, for example for some small directories. >> 3) any column of table or view field (including not foreign keys) with >> #REFERENCES#<table_name>.<fieldname># is a foreign key > > This doesn't seem like a good idea for me. Have you other ideas? PS I've already ported my database back to MSSQL because of problem with FbCommand finalization and FB performance issues :-/ I've tried to fix FbCommand.Dispose(bool disposing) with adding additional null checkings, but it didn't help. MS provider working correctly... ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
