On Mon, 27 Oct 2003 15:24:37 -0500, Priyanka Gupta <[EMAIL PROTECTED]> wrote:
Is there a way in mYSQL to just define an auto increment sequence rather than defining
a field inside a table which is an auto increment. Bsically I need some functionality
similarto that in ORACLE where CREATE SEQUENC
thank you all for your help,
this was the explanation I needed,
>LAST_INSERT_ID() with an argument creates a value that can be treated
>just like it's an AUTO_INCREMENT value. That means you can call
>LAST_INSERT_ID() without an argument later in the current session to
>retrieve the value you
At 1:49 PM +0200 6/26/01, Gunnar von Boehn wrote:
>Hello everybody,
>
>
>I thing, that I have a problem that needs a sequence and that
>auto-increment can't do the job this time.
>
>I already consulted the manual and the mailarchive.
>I saw several different proposals, now I'm a bit confused and d
On Tuesday 26 June 2001 04:49, Gunnar von Boehn wrote:
> Hello everybody,
>
>
> I thing, that I have a problem that needs a sequence and that
> auto-increment can't do the job this time.
>
> So, I think the only way to solve this is a sequence table.
>
> Lets take a single row, integer value for h
Hi Gunnar,
Why don't you keep the key out of the business rule and create a column to
identify the type of customer?
How are you going to handle the application when your business reaches more
than vip customers???
This is an issue that can be avoided by creating a type column .
Siomara
At 13:49 +0200 2001-06-26, Gunnar von Boehn wrote:
>Lets take a single row, integer value for holding the sequence:
>CREATE TABLE sequence(
> id int4;
>);
That works, though I would use a single table for all sequences, not
a new table per sequence.
The other solution would be to do check the
