On Thu, Jul 2, 2009 at 14:08, sasha<[email protected]> wrote:
> 1) This question should be discussed in fb-devel and i think that new
> feature should be added to server for this
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.
> 2) I think that special table will be better solution than comments
Why?
> 3) Have you thought about views? There are big problems with views too,
> because provider dont't know abbout any relations, key fields and
> autoincrements for wiews.
Because view has relations etc.
> So, i'd like to propose to make some special tables like this:
>
> _AUTOINCREMENTS (FIELD_NAME, GENERATOR_NAME)
>
> _VIEW_PRIMARY_KEYS (VIEW_NAME, FIELD_NAME)
>
> _VIEW_FOREIGN_KEYS (VIEW_NAME, FIELD_NAME, REFERENCE_RELATION,
> REFERENCE_FIELD_NAME)
Why somebody would clutter database with this? What about keys on more
than one column, etc. etc. etc. And keeping this in sync (and between
FB versions - like different length for column names, which is
probably going to happen).
Yes, this is definitely not going to happen.
We need just a small hack, not just complete system tables replacement.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
