pmadb compatible between 3.5 and 4.0?

[Joe Pruett]

if i set my config to use the same pmadb tables for a 3.5 install and a
4.0 install, is that going to be ok? it looks like the structures are
the same, just the names changed to add an extra underscore. i want to
give people the ability to try 4.0 but still have their saved queries, etc.

[Isaac Bennetch]

Hi,

Post by Joe Pruett
if i set my config to use the same pmadb tables for a 3.5 install and a
4.0 install, is that going to be ok? it looks like the structures are
the same, just the names changed to add an extra underscore. i want to
give people the ability to try 4.0 but still have their saved queries, etc.

The names are completely configurable. Since you already have the
tables, if you copy over your old config.inc.php (or copy only the
relevant chunks, anyway), you should have a very painless upgrade.
phpMyAdmin will warn you if your table structure is outdated.

Yes, the default now has double underscores now, but that shouldn't
affect you unless you re-run the setup script (you can edit it to use
your existing table names).

[Joe Pruett]

Post by Isaac Bennetch
Hi,

Post by Joe Pruett
if i set my config to use the same pmadb tables for a 3.5 install and a
4.0 install, is that going to be ok? it looks like the structures are
the same, just the names changed to add an extra underscore. i want to
give people the ability to try 4.0 but still have their saved
queries, etc.

The names are completely configurable. Since you already have the
tables, if you copy over your old config.inc.php (or copy only the
relevant chunks, anyway), you should have a very painless upgrade.
phpMyAdmin will warn you if your table structure is outdated.
Yes, the default now has double underscores now, but that shouldn't
affect you unless you re-run the setup script (you can edit it to use
your existing table names).

i was really concerned about sharing between versions, but i went ahead
and tested and things look ok so far.