This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Normal 0 false false false EN-US X-NONE HE
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;}
Hi, The lightspeed Schema Migrations is great but.... Do you have any support for Data Migrations? Any best practices over production server? Did I miss something in the documentation? Thanks
|
|
|
|
|
We don't have special support in Migrations for data migration, but there are a couple of ways you can do it: 1. Use LightSpeed! Add code to your migration to create a unit of work, load existing data if necessary, process it, and save the changes. This works well for initialising tables (e.g. reference data) or for changes to existing columns, but may be a bit tricky if you are changing the set of columns. 2. Use ExecuteNativeCommand to run custom SQL during the migration. This gives you maximum flexibility but may require tweaking to different databases if your app supports more than one database engine. |
|
|
|
