Re: [SQLObject] naming conventions

[Ian B. <ia...@co...>]

On Wed, 2003-04-30 at 12:11, Luke Opperman wrote:
> This gets to a current struggle in SQLObject over whether to name
> things by SQL convention or Python convention. It's split right now,
> but for instance:
> 
> notNull vs notNone
> TextCol/CharCol vs StringCol

Yeah, it's notNull now, but if I stick with Python types it should
really be notNone (which isn't bad, actually).  Maybe I'll make that
change before 0.4.

I'm not sold on using Python types, though I suspect there will be more
confusion if I use SQL types (like DateTimeCol in MySQL, vs.
TimestampCol in Postgres).  We can all agree on the Python types,
because there's only one Python, but there's many databases, not all of
which adhere to the SQL standard (DBMConnection obviously does not, for
instance, nor would MetaKit).

  Ian