<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: MySQL Database versioning strategy</title>
	<atom:link href="http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/</link>
	<description>Just another developer blog</description>
	<lastBuildDate>Thu, 29 Jul 2010 03:41:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/comment-page-1/#comment-7482</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Fri, 17 Apr 2009 15:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=374#comment-7482</guid>
		<description>At the moment the table exists in every installation. 

To do an update we dump the latest data from our development system and insert it into the table on the live installations. 

This is fine as the data is only ever created by the development team and will never be editable by anyone else. 

I am looking at improving things though by having a central database that all installations &quot;phone home&quot; to so we only have the data in one place.</description>
		<content:encoded><![CDATA[<p>At the moment the table exists in every installation. </p>
<p>To do an update we dump the latest data from our development system and insert it into the table on the live installations. </p>
<p>This is fine as the data is only ever created by the development team and will never be editable by anyone else. </p>
<p>I am looking at improving things though by having a central database that all installations &#8220;phone home&#8221; to so we only have the data in one place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabi Solomon</title>
		<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/comment-page-1/#comment-7481</link>
		<dc:creator>Gabi Solomon</dc:creator>
		<pubDate>Fri, 17 Apr 2009 14:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=374#comment-7481</guid>
		<description>but what do you do on production websites ? ... do you still have that table</description>
		<content:encoded><![CDATA[<p>but what do you do on production websites ? &#8230; do you still have that table</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/comment-page-1/#comment-7480</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Fri, 17 Apr 2009 11:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=374#comment-7480</guid>
		<description>Hi,

I&#039;ve been looking at this recently and have something similar but the changeset data is in a database table of the form:

CREATE TABLE `system_upgrade` (
  `id` int(11),
  `from` decimal(5,2),
  `to` decimal(5,2),
  `type` enum(&#039;db&#039;, &#039;php&#039;),
  `upgrade` text ,
  `comments` varchar(255),
  PRIMARY KEY  (`id`)
) TYPE=MyISAM;

Every time we make a change we put the SQL in this table and then use a web interface to upgrade other sites. Its in its infancy but works well.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve been looking at this recently and have something similar but the changeset data is in a database table of the form:</p>
<p>CREATE TABLE `system_upgrade` (<br />
  `id` int(11),<br />
  `from` decimal(5,2),<br />
  `to` decimal(5,2),<br />
  `type` enum(&#8216;db&#8217;, &#8216;php&#8217;),<br />
  `upgrade` text ,<br />
  `comments` varchar(255),<br />
  PRIMARY KEY  (`id`)<br />
) TYPE=MyISAM;</p>
<p>Every time we make a change we put the SQL in this table and then use a web interface to upgrade other sites. Its in its infancy but works well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabi Solomon</title>
		<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/comment-page-1/#comment-7472</link>
		<dc:creator>Gabi Solomon</dc:creator>
		<pubDate>Tue, 14 Apr 2009 07:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=374#comment-7472</guid>
		<description>@Jani
I dont know how you can make that more automatic either.
And i access the script to update my working copy .. .for stanging and production its automated. ( post-commit script )

I will look into posting my classes elsewhere since there are a lot of people bothered ny the login ... but dont expect to much of the class ... it just reads the files and do a mysql querry :)</description>
		<content:encoded><![CDATA[<p>@Jani<br />
I dont know how you can make that more automatic either.<br />
And i access the script to update my working copy .. .for stanging and production its automated. ( post-commit script )</p>
<p>I will look into posting my classes elsewhere since there are a lot of people bothered ny the login &#8230; but dont expect to much of the class &#8230; it just reads the files and do a mysql querry <img src='http://www.gsdesign.ro/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jani Hartikainen</title>
		<link>http://www.gsdesign.ro/blog/mysql-database-versioning-strategy/comment-page-1/#comment-7470</link>
		<dc:creator>Jani Hartikainen</dc:creator>
		<pubDate>Tue, 14 Apr 2009 01:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsdesign.ro/blog/?p=374#comment-7470</guid>
		<description>Nice idea. Personally I&#039;d prefer if the 1123 numering scheme would be more automatic, because it&#039;s a bit tedious in my opinion to maintain such directory structure. Not sure how you could achieve that though.

Also, rather than using your own script, how about using Phing for deploying the changes? Phing has a DbDeploy task type which could possibly be used for something like that. (see http://phing.info/docs/guide/current/ Appendix B)

ps. I wanted to take a look at your script, but phpclasses wanted me to log in. I don&#039;t have a phpclasses account and 99% of stuff from there isn&#039;t worth it, so I kinda don&#039;t want to make one... =)</description>
		<content:encoded><![CDATA[<p>Nice idea. Personally I&#8217;d prefer if the 1123 numering scheme would be more automatic, because it&#8217;s a bit tedious in my opinion to maintain such directory structure. Not sure how you could achieve that though.</p>
<p>Also, rather than using your own script, how about using Phing for deploying the changes? Phing has a DbDeploy task type which could possibly be used for something like that. (see <a href="http://phing.info/docs/guide/current/" rel="nofollow">http://phing.info/docs/guide/current/</a> Appendix B)</p>
<p>ps. I wanted to take a look at your script, but phpclasses wanted me to log in. I don&#8217;t have a phpclasses account and 99% of stuff from there isn&#8217;t worth it, so I kinda don&#8217;t want to make one&#8230; =)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
