Andreas Flack writes: >> Also you can set LogLevel to 'message' before running midgard-schema. >> It will produce nice messages about what table is created/already >> exists, and what column is created/already exist. > > I had tried that before, but all I got was a memory access error. The > funny thing is that I tried it again now, and it ran without problems. > Now, the errors have disappeared, so I guess everything is fine again.
Please report it next time :) > BTW: I saw some warnings in the log file. I don't know if they're > interesting, but I thought I'd post them here: > > Schema (pid:16518):(m): Type net_nemein_tag_link > midgard-core (pid:16518):(m): Table and columns for > 'net_nemein_tag_link' OK > midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column > 'fromClass' used in key specification without a key length It's harmless AFAIK. Core's table creation is not smart enough to handle already user's created/updated columns if they do not match core's way to do it. Piotras _______________________________________________ user mailing list [email protected] http://lists.midgard-project.org/mailman/listinfo/user
