On Fri, Jul 3, 2009 at 13:00, sasha<[email protected]> wrote:
> Why autoincrement fields can't be created with help of generators and
> special system triggers (as it made for CHECK constraints)?
It can. But it's not solving the problem of using "normal" trigger and
using it for creating PK value. And this is the problem we're talking
about.
> Because all will be in one independent place and will be available for
> editing.
Why is independent place better than system tables properly maintained
by engine?
> Yes, but this cause similar problem for designer. Each model updating
> will drop all hand-made changes.
Yes, but there's actually no relation in database. View has no
relation, so it's not in result. Even MS SQL has not this.
> Why somebody should clutter database with comments?
Comments are there. You don't have to add anything.
And if you leave the comment empty, it will just work as right now.
With some special tables you'll need to add it there first. And did
you think about RO databases? Or databases you're not allowed to add
tables in?
> > 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.
With this argument we can easily say, that everytime after model
update, it's developers problem to put back generated PKs.
--
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
