On Mon, Mar 29, 2010 at 12:34, sasha <trofim...@gmail.com> wrote:
>>> 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.
I'm still not convinced. Sure you can ensure the field is de-facto PK,
but as it's more walking on thin ice than robust design I think you,
as developer, should modify your model accordingly and keep it.
Sometimes I change SSDL parts of model manually. But as I know it's
hack, I watch carefully every my commit to SVN to ensure, it's still
there and makes sense.
>>> 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?
Nope. :) I don't think it's good idea at all, not just only bad design.
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
