>Oops, seems like a bug. I think what caused the bug is using
> fromDatabase and idName simultaneously - SQLObject drew SystemName from the
> DB and added it because of the idName. To work around the bug avoid
> using fromDatabase - declare your columns explicitly.
Thanks for the explanation.
On Tue, Jul 22, 2008 at 02:06:06PM +0400, Oleg Broytmann wrote:
> > Maybe I can remove SystemName from the column list
>
>Columns are in SystemsInfo.sqlmeta object (see main.py), in .columns,
> .columnList, .columnDefinitions.
And there is SystemsInfo.sqlmeta.delColumn() call.
Oleg.
--
On Mon, Jul 21, 2008 at 05:31:24PM -0700, Ray Van Dolson wrote:
> class SystemsInfo(SQLObject):
> class sqlmeta:
> fromDatabase = True
> table = 'SystemsInfo'
> idType = str
> idName = 'SystemName'
> lazyUpdate = True
>
> So, my "id" key has been changed to SystemName. In th
On Mon, Jul 21, 2008 at 05:31:24PM -0700, Ray Van Dolson wrote:
> Hi all, I'm running into an exception trying to create a new row in a
> table with fromDatabase = True defined (the table is pre-existing).
Hmm, I am guessing the note right above this:
http://www.sqlobject.org/SQLObject.html#cla
Hi all, I'm running into an exception trying to create a new row in a
table with fromDatabase = True defined (the table is pre-existing).
The class definition looks like this:
class SystemsInfo(SQLObject):
class sqlmeta:
fromDatabase = True
table = 'SystemsInfo'
idType = str
idN
