| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
* Added an error message in initial estate owner creation that makes it clear what needs to happen.
|
| |
|
| |
|
|
|
|
| |
better
|
|
|
|
| |
(some Estate SQL left behind in the Region migration)
|
|
|
|
|
|
|
|
|
|
|
|
| |
ok, so the estate stores now want their own migration files, but as it
happened the SQL definition were inside the Region migrations.
It seems better/cleaner to keep each 'store' separately updatable.
WARNING: any editing in the middle of the migration scripts (as opposite
to just appending to them) has the potential of messing up updates of
existing databases. As far as I can see, this one is (probably) safe,
the worst that could happen is the EstateStore migration silently fail
if the estate the tables are already there.
|
|
|
|
| |
files. Restored Presence table to its taboo-breaking form.
|
|
Replaced all NNN_StoreName.sql migration resources with a more
readable, single-file-per-store
|