On 4/4/06, Patrick Coleman <[EMAIL PROTECTED]> wrote:
ummm that is ugly, that's why packages where invented ;)
I believe the correct way is to change SQLObject so it has _ on all base methods
This is one of the problems if SQLObject that SQLAlchemy solves.
No it is a bug in SQLObject/python I never like that overwrite feature anyway
On 4/4/06, Jorge Vargas <[EMAIL PROTECTED]> wrote:
> On 4/4/06, Patrick Coleman <[EMAIL PROTECTED]> wrote:
> > My database has a column 'expire' in a certain table. It appears that
> > when SQLObject calls expire() (line 778, dbconnection.py) on a cache
> > object from that table,
>
> oh we should do something about those either as a patch to sqlobject or
> build into TG, there should be a list of invalid column names and fail to
> create the tables grafully, maybe with an exception.
It would be better (IMHO) to change the SQLObject methods so they
don't use common words, perhaps by prepending 'SQLObject__' or
something. Better than that change SQLObject somehow so it doesn't get
confused between database columns and internal methods. I understand
that both of these options would probably be major undertakings, but
if the alternative is saying people can't have columns called 'expire'
(or who knows what other names lurking in the murky depths of the
SQLObject source :) then I'm all for it.
ummm that is ugly, that's why packages where invented ;)
I believe the correct way is to change SQLObject so it has _ on all base methods
This is one of the problems if SQLObject that SQLAlchemy solves.
In my case, a particular piece of software (MyDNS) requires that the
database layout be exactly what it expects, so changing the database
to suit SQLObject isn't an option. Call it a bug in MyDNS if you like,
but highly I doubt I'm the only one in this situation.
No it is a bug in SQLObject/python I never like that overwrite feature anyway
> > rather than calling the expire method to expire
> > the object from cache it actually returns the value from the 'expire'
> > column, which being a Long of course isn't callable, hence the
> > exception above.
>
> that is one feature of python going wrong ...
Certainly is :)
Cheers,
Patrick
--
http://www.labyrinthdata.net.au
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
