On Tue, Jan 23, 2007 at 04:46:50PM -0300, Leandro Lucarella wrote:
> Sender: phd
> > clauseTables must be a sequence of tables names (strings), not
> > objects.
>
> So, if Table object is not suitable for use with clauseTable, what is it
> for?
It is used internally in SQLObject. In q-magic, e.g.
> The only thing SQLBuilder documentation has, is the Table object, so
SQLObject docs really need update. :(
> I don't know, I find cleaner (and pythonic) to use something like:
>
> my_table = sqlbuilder.table.a_table
>
> clauseTables=(my_table, Plan.sqlmeta.table)
>
> than:
>
> my_table = sqlbuilder.table.a_table
> my_table_str = str(my_table)
>
> clauseTables=(my_table_str, Plan.sqlmeta.table)
>
> because I use my_table to construct other sql expressions.
There is an assumption that clauseTables is a list of *strings*. If you
want to change this you have to remove this assumption from
dbconnection.py.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
