On 22 ago, 19:29, jason kirtland [EMAIL PROTECTED] wrote:
Anil wrote:
Actually, there was some information in the logs that I just noticed
that might help detect the problem (some kind of unicode issue?):
12:58:21,710 INFO [sqlalchemy.engine.base.Engine.0x..50] SHOW CREATE
TABLE `User`
pablo wrote:
Sorry, but I'm still having the same issue. I updated only the
file in the changeset and the error keeps appearing. I'm missing
something?
That table is reflecting without issues for me in the trunk. Are
you seeing the same warning in the log?
Hi Anil,
The recent 0.4 betas have an all-new MySQL table reflection routine
that's being tried out. It's possible that it's not picking up
your primary key when it should- could you send in the output of
SHOW CREATE TABLE for this table, either on or off list? Also
there should be a
| User | CREATE TABLE `User` (
`id` int(10) unsigned NOT NULL auto_increment,
`location_id` int(10) unsigned NOT NULL,
`mail` varchar(45) NOT NULL,
`password` varchar(45) NOT NULL,
`salt` varchar(8) NOT NULL,
`phone` varchar(24) default NULL,
`organization` varchar(45) default
Anil wrote:
Actually, there was some information in the logs that I just noticed
that might help detect the problem (some kind of unicode issue?):
12:58:21,710 INFO [sqlalchemy.engine.base.Engine.0x..50] SHOW CREATE
TABLE `User`
12:58:21,711 INFO [sqlalchemy.engine.base.Engine.0x..50]
