> -----Original Message-----
> From: Andre Schild [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 05, 2001 1:24 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Antw: Torque/Sybase updates
>
>
> >Hmm, not following you here. Wouldn't the generated turbine
> schema just use
> >the idbroker for autoincrement keys?
> Why not let the database handle this stuff ?
> A problem is, that as example the sybase-turbine-security.sql
> script inserts teh default user in the TURBINE_USER table,
> but the ID is not specified, so we need the value be
> generated from the database.
There are arguments for and against using db specific increment vs.
Turbine's IDBroker, that is why Turbine is written to handle both. For the
ASE/ASA case maybe it would be best to default to IDBroker in db.props,
since I believe this is the default when generating the schema for Turbine
in other db's. Maybe someone else would like to comment? We could even put
some comments in the db.props about using IDENTITY if a user so desires.
> >Also, the builtin for ASE is the IDENTITY modifier on the column.
> >Maybe I'm confused...
> Here what the ASA 6.0 docu tells about this:
>
> In Adaptive Server Anywhere the identity column and the
> AUTOINCREMENT default setting for a column are identical.
>
> So we can use the IDENTITY in the properties file, since ASA
> does translate this into a DEFAULT AUTOINCREMENT
As far as I can tell, as of ASE 11.x, IDENTITY is the name and the datatype
must be NUMERIC for ASE to autoincrement.
jb
------------------------------------------------------------------------
This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
