Re: [SQLObject] _idName

2006-12-22 Thread Oleg Broytmann
On Mon, Dec 11, 2006 at 09:03:04AM +0100, Robert wrote: > Oleg: this gives you no control over actual table names. I forgot to > mention this is a must as well, we have tables from an external source > (exported from another DBMS) that are used by some other software too. I fixed this in the

Re: [SQLObject] _idName

2006-12-12 Thread Oleg Broytmann
On Mon, Dec 11, 2006 at 09:03:04AM +0100, Robert wrote: > Oleg: this gives you no control over actual table names. I have found the root of the problem: class common_sqlmeta(sqlmeta): idName = "my_id" class Test1_sqlmeta(common_sqlmeta): table = "my_test_11" print common_sqlmeta.idName

Re: [SQLObject] _idName

2006-12-11 Thread Robert
Luke: this would be the obvious solution if it did work (this actually was the first thing I tried), alas no go, at least on 0.7.0 and 0.7.1. Oleg: this gives you no control over actual table names. I forgot to mention this is a must as well, we have tables from an external source (exported from

Re: [SQLObject] _idName

2006-12-08 Thread Luke Opperman
s structure specification is that each table has the > same primary key name. Thus, it would be nice to have the id name > declared inside the class scope, not in the sqlmeta, like this: > > class A(SQLObject): > _idName = "Ident" > # a lot of other definitions: fields,

[SQLObject] _idName

2006-12-08 Thread Robert
part of the class structure specification is that each table has the same primary key name. Thus, it would be nice to have the id name declared inside the class scope, not in the sqlmeta, like this: class A(SQLObject): _idName = "Ident" # a lot of other definitions: fields, ins