Piotr Pokora schrieb:
Andreas Flack writes:
Hi!
Hi!
The database in question was just updated from 2.6 running on a
different server, where none of the components in question where
installed (so the tables are all empty and so far unused). I ran
datagard update multiple times and have TableCreate and TableUpdate set
to true in the config file, but this doesn't fix those problems.
TableCreate and TableUpdate are midgard-schema related.
So set them to true and run `midgard-schema configname` instead of datagard.
Please, update to 1.8.7 before doing this as table create/update is
highly improved there.
I already upgraded to 1.8.7 before upgrading. But apparently, it didn't
help :-)
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.
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
Schema (pid:16518):(m): Type midcom_core_group_virtual_db
midgard-core (pid:16518):(m): Table and columns for
'midcom_core_group_virtual_db' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'component' used in key specification without a key length
Schema (pid:16518):(m): Type midcom_core_privilege_db
midgard-core (pid:16518):(m): Table and columns for
'midcom_core_privilege_db' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'name' used in key specification without a key length
Schema (pid:16518):(m): Type midcom_core_login_session_db
midgard-core (pid:16518):(m): Table and columns for
'midcom_core_login_session_db' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'userid' used in key specification without a key length
Schema (pid:16518):(m): Type org_openpsa_notifications_notification
midgard-core (pid:16518):(m): Table and columns for
'org_openpsa_notifications_notification' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'action' used in key specification without a key length
Schema (pid:16518):(m): Type org_openpsa_relatedto
midgard-core (pid:16518):(m): Table and columns for
'org_openpsa_relatedto' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'toClass' used in key specification without a key length
Schema (pid:16518):(m): Type org_openpsa_person
midgard-core (pid:16518):(m): Table and columns for 'org_openpsa_person' OK
midgard-core (pid:16518):(WARNING): query failed: Specified key was too
long; max key length is 1000 bytes
Schema (pid:16518):(m): Type org_openpsa_calendar_resource
midgard-core (pid:16518):(m): Table and columns for
'org_openpsa_calendar_resource' OK
midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
'location' used in key specification without a key length
Bye, and thanks again!
Andreas
You can "redirect" all message from terminal to LogFile which is also
configurable.
Piotras
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
