🚀 go-pugleaf

Hi !!!
I think that it is one of the right way to solve AutoInc fields problem. But
this statement:

SELECT gen_id(generator_name,1), COUNT(*) FROM  table_name

will decrease perfomance of the application if table you are selecting from
has lots of records.

So I'd like to suggest the following solution:
1. In database should be created special table with only record.
2. Select statement should be changed as follows:
SELECT gen_id(<generator_name>, 1) from <name_of _table_with_only_record>

Best Regards !!!

Umberto Uderzo <umberto@uderzo.it> wrote in message news:3b40f10e_2@dnews...
> Hi Francesco,
>
> Thanks for descripting your approach to the problem. Personally i've
adopted
> another tehnique (sure it's not much portable, but it will be easily
adapted
> for other DBMS): instead of using a generator into a trigger to autoset
the
> primary key value (this causes problems trying to refresh the autoinc
field)
> i perform directly the query SELECT gen_id(generator_name,1), COUNT(*)
FROM
> table_name, where gen_id is a proprietary sintax of Interbase used to get
an
> unique id from a <generator_name> generator that doesn't suffer multiuser
> troubles, and COUNT(*) is used as grouping function to avoid the result of
> generating as many new id as the rows of the table <table_name>, used here
> only to respect the select syntax.
> I repeat, not so portable, but easily replaceable with your technique if
> needed (just isolating the entire id generation process into a private
> session).
>
> Ciao... Umberto Uderzo
>
> P.S. I think it's a bit dangerous to rollback the id rows values as you
say.
> To have a sure robust mechanism i suggest to increment always and anyway.
> So: perform the increment step in a separate session.
>
> "Formentz" <francesco@leotron.com> ha scritto nel messaggio
> news:3b3c7c38_1@dnews...