SQLObject

On Monday 23 May 2005 04:07, Faber wrote:

> How can I use SQLObject in order to represent a table with multiple
> fields as primary key? Such as:
>
> CREATE TABLE Test (
> 	First VARCHAR(20) REFERENCES OtherTable,
> 	Second VARCHAR(50),
> 	PRIMARY KEY (First, Second)
> )

I refresh the question, because SQLObject is not usable on these contexts; =
I=20
can't use the set() method because SQLObject does a WHERE clause only on=20
the first column.

Please tell me if I can avoid this or if I have to build my UPDATE SQL=20
manually.

Thank you  ^__^

=2D-=20
=46aber
http://www.faberbox.com/

New processes are created by other processes, just like new=A0humans.
New=A0humans are created by other humans, of course, not by processes. -- U=
nix=20
System Administration Handbook

On Thu, Jun 02, 2005 at 03:55:46PM +0200, Faber wrote:
> I refresh the question, because SQLObject is not usable on these contexts; I 
> can't use the set() method because SQLObject does a WHERE clause only on 
> the first column.

   No, SQLObject cannot manipulate tables with compound (multi-column)
primary keys.

> Please tell me if I can avoid this or if I have to build my UPDATE SQL 
> manually.

   IWBN if someone extends SQLObject in this aspect...

Oleg.
-- 
     Oleg Broytmann            http://phd.pp.ru/            phd@...
           Programmers don't die, they just GOSUB without RETURN.

On Thursday 02 June 2005 16:08, Oleg Broytmann wrote:

[cut]

>    No, SQLObject cannot manipulate tables with compound (multi-column)
> primary keys.
>
> > Please tell me if I can avoid this or if I have to build my UPDATE SQL
> > manually.
>
>    IWBN if someone extends SQLObject in this aspect...

I hope to have some spare time for working on that, but I fear I can't...

Thank you for the clarification, anyway  :)

-- 
Faber
http://www.faberbox.com/

When replying to a message, include enough original material to be 
understood but no more. It is extremely bad form to simply reply to a 
message by including all the previous message: edit out all the irrelevant 
material. -- S. Hambridge, RFC 1855