Re: [Serusers] register_udomain(): Invalid table version (use ser_mysql.sh reinstall)

What's amusing is WHY this comes up. I'm not entirely sure the table check code is right (or it may be correct, but it's not exactly rational). For instance, the a month or two ago, we were switching from using lookup("aliases") to alias_db_lookup("dbaliases") as our alias check (porting the code from openser to ser). There was a spot in the config where we'd forgotten to change the command from lookup to alias_db_lookup, but had changed the table name from aliases to dbaliases. What happens? Out pops the 'register_udomain() Invalid table version' error. Now, I'm not sure what it's checking for in that case, but I can tell you that THAT error message (and the advice it gives to use the reinstall option of the mysql script) is entirely NOT helpful. :) To play around, I added a version entry for dbaliases and matched its version to the aliases table just to see if indeed that was the result of a version check. No dice. What it apparently was doing was checking the format of the dbaliases table against its expected format (aliases is VERY different in format) and spitting out an error that the table version was incorrect. Um... no... the table STRUCTURE was incorrect, but that really has nothing at all to do with the version per se. I'm thinking that perhaps the version table with its version numbers to denote some sort of extra check on the tables is, perhaps, not the best way to do things. At the very least, there ought to be more applicable error messages when a structure check fails. Something like "aliases table not proper structure for lookup() command" would have been the most ideal error message of course. I'd have known in a heartbeat where the problem was. Someone who DIDN'T know what he was doing might have spent all day trying to install/reinstall the DB as per instructions in the error message (which don't work), and would still have gotten nowhere. N. On Fri, 15 Sep 2006 10:48:08 +0100, bails wrote