| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Thank you, RuudL, for a complete adaptation of migration and estate
data to MSSQL, and the updating of the RegionData handling in MSSQL.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* commented out [Obsolete(....)] attributes where no replacement feature
was available: if we want to attribute code that we think needs to be
reworked, we should define a new attribute and use that instead
(together with a little tool to retrieve all the attributed code then)
* commenting out unused variables
|
|
|
|
|
|
|
| |
migrations (like converting asset ids) don't run into the
normal 30 second kill switch.
|
|
|
|
|
|
| |
side so that people don't think we're hung.
|
|
|
|
|
|
|
|
|
|
| |
changes it wouldn't come up).
include embedded dialect specific sql files for nhibernate migrations
figure out how to get the raw db connection so that migrations can
work with nhibernate.
create initial migration for NHibernate + SQLite + Assets.
|
|
|
|
|
|
| |
more clear
|
|
|
|
|
|
|
|
|
| |
asset uuids no longer binary. I've tested this migration a
few times, and it seems working in all the scenarios I've found
but it wouldn't hurt to backup your asset db before running this
as it does touch a very sensitive part of our content system.
|
|
|
|
| |
hard-coded port numbers.
|
|
|
|
|
|
|
|
| |
is now using migrations instead of the old model to
create tables. Tested for existing old tables,
and for creating new ones.
|
|
|
|
|
|
|
| |
migrating from the old to the new system. Silly legacy
code.
|
|
|
|
|
|
|
| |
tracking, and support sub types that we'll need for
nhibernate.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Tomorrow I'll start trying to integrate them into sqlite
to see if this works right for table migration.
|
|
really turned out to be small enough to not need it's own
assembly
|