Ah yes, I remember that now.

Correct me if I'm wrong, but the idbroker was doing autoincrement for
any primary key/ints. And the native wasn't, so your patch made it
consistent.

So, I'm ready to spend the time fixing idbroker to only apply to fields
marked as autoincrement. Then backing out your patch would make it
consistent...you have to have autoincrement=true for any idbroker/native
autoincrementing to happen.

So again, we're getting into a thorny semantics debate, but I don't
think the defaultIdMethod should have any affect on whether a field
autoincrements or not.

Primary keys are usually defined as unique and not null. Autoincrement
is something completely different than a primary key. defaultIdMethod
can say how autoincrement is achieved, but I think only in fields where
autoincrement is already specified.

People familiar with databases know that primary keys and autoincrement
are two separate things. I think blurring the line and having some
obscure rule that all primary key/int fields are autoincrement depending
on what defaultIdMethod is set to will only confuse people. It has
confused and still is confusing to me, at least.

You can make the argument that good database design dictates this or
that, or that most everyone uses primary key/ints/autoincrements in this
same way, but it still conflicts with a basic understanding of database
principles.

Sound good?

Thanks,
Stephen

> -----Original Message-----
> From: James Turner [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, July 27, 2002 5:38 PM
> To: [EMAIL PROTECTED]
> Subject: Re: autoincrement fiasco
> 
> On Sat, 27 Jul 2002 17:09:37 -0500 "Stephen Haberman" wrote:
> 
> > What makes the mysql columns.vm special enough to handle have the
extra
> > native/integer primary key code that most of the other columns.vm
don't
> > have?
> 
> Because a month or so ago I contributed the patch that made it work
for MySQL.
> 
> James
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:turbine-torque-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-torque-dev-
> [EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to