| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | try again to update SQLite estateban | UbitUmarov | 2019-08-18 | 1 | -3/+2 |
| | | |||||
| * | try to update SQLite estateban | UbitUmarov | 2019-08-18 | 1 | -0/+9 |
| | | |||||
| * | Flatten migrations for sqlite | Diva Canto | 2016-02-21 | 1 | -48/+20 |
| | | | | | | | Conflicts: OpenSim/Data/SQLite/Resources/RegionStore.migrations (Resolved) | ||||
| * | Send up the part missing from the Avination Estate commit. | Melanie | 2013-05-11 | 1 | -0/+9 |
| | | | | | Warning - contains a small migration. | ||||
| * | Split migrations for RegionStore and EstateStore (see WARNING!) | AlexRa | 2010-05-23 | 1 | -0/+88 |
| 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. | |||||
 |
index : opensim-SC | |
| My fork of OpenSim for IG and DG, called SledjChisl. |
| aboutsummaryrefslogtreecommitdiffstatshomepage |