Re: [SQLObject] Style issues

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

On Mon, 2003-05-05 at 10:03, Luke Opperman wrote:
> Hello -
> 
> Having some issues with application of styles and changed behavior
> from the previous default 'style'. (This is all from CVS late last
> week..)
> 
> 1. Double capitals in table and column names are treated differently
> from before: ie, 'PProductXType' used to generate 'p_product_x_type',
> now generates 'pproduct_xtype'. It's not a very pretty name by
> itself, but the new conversion is fairly unexpected to me regardless.
> Simple changes to the RE ('[A-Z]' instead of '[A-Z]+') and not
> treating tablenames different from column names fixes these. In
> general I guess we may start using our own style object, but I'm just
> concerned that the new default Style breaks old (simpler) behavior.

Okay, that should be fixed.  I wanted it to be like HTMLName ->
html_name, which should be the present behavior (and PProductXType ->
p_product_x_type)

> 2. '_defaultOrder' in 0.3 and in my original suggestion would accept
> either database-style or python-style names. It now assumes it is in
> database-style. Simple fix is to put check that used to be in the
> metaclass back in (modified to use styles):

This should be fixed too.  More generally, it checks if you give a
column name in the orderBy argument, and if so gets the .dbName.

  Ian