On 27-8-2013 20:22, Adriano dos Santos Fernandes wrote: > The user issue is about managing the internal generator. > > You can do it now, but you need to discover its internal name. > > Why complicate things? > > Identity columns allows the use to put manually generated values. So the > ability to manage a sequence is a must-have. > > And if a object can be managed, it must have a known name. It's exactly > like constraints/indexes, so what's wrong?
I'd be interested to know why it was chosen to implement GENERATED BY DEFAULT AS IDENTITY instead of (or: and not also) GENERATED ALWAYS AS IDENTITY. To be honest I think that generated always is usually a better choice (although I have to admit that I have abused SET IDENTITY_INSERT <table> ON in SQL Server). Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
