Thread: postgresl for mysql?
What will they think of next! http://krow.livejournal.com/502908.html I suppose it makes as much sense as the others, except why would you want to use mysql if the storage is in postgres? Cheers Anton
On Apr 1, 2007, at 10:33 AM, Anton Melser wrote: > What will they think of next! > http://krow.livejournal.com/502908.html > I suppose it makes as much sense as the others, except why would you > want to use mysql if the storage is in postgres? If you've inherited data in a postgresql database this will allow you to migrate it to the industry standard database without the inconvenience and downtime of a dump from postgresql and a restore into mysql. I don't think it's a new idea - IIRC, Aprile Pazzo did something similar for MySQL 3 and PG 7.something. Cheers, Steve
On 4/1/07, Anton Melser <melser.anton@gmail.com> wrote: > What will they think of next! > http://krow.livejournal.com/502908.html > I suppose it makes as much sense as the others, except why would you > want to use mysql if the storage is in postgres? > Cheers > Anton > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > Is today Aprils Fool's ? -- Leonel
Leonel <lnunez@gmail.com> writes: > On 4/1/07, Anton Melser <melser.anton@gmail.com> wrote: >> What will they think of next! >> http://krow.livejournal.com/502908.html > Is today Aprils Fool's ? Yup. But he got me for about half a second, because this was proposed entirely seriously by the MySQL AB folk back when they were looking for a way out from under Oracle's purchase of InnoDB. Since they hired Jim Starkey to write "Falcon" for them, I don't think there's any interest in that anymore over there. regards, tom lane
OK, it got me for more than half a second... :-) And as you mention - not entirely ridiculous! Cheers Anton On 01/04/07, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Leonel <lnunez@gmail.com> writes: > > On 4/1/07, Anton Melser <melser.anton@gmail.com> wrote: > >> What will they think of next! > >> http://krow.livejournal.com/502908.html > > > Is today Aprils Fool's ? > > Yup. But he got me for about half a second, because this was proposed > entirely seriously by the MySQL AB folk back when they were looking for > a way out from under Oracle's purchase of InnoDB. Since they hired Jim > Starkey to write "Falcon" for them, I don't think there's any interest > in that anymore over there. > > regards, tom lane >
On Sun, Apr 01, 2007 at 10:53:06AM -0700, Steve Atkins wrote: > > On Apr 1, 2007, at 10:33 AM, Anton Melser wrote: > > >What will they think of next! > >http://krow.livejournal.com/502908.html > >I suppose it makes as much sense as the others, except why would you > >want to use mysql if the storage is in postgres? > > If you've inherited data in a postgresql database this will allow > you to migrate it to the industry standard database without the > inconvenience and downtime of a dump from postgresql and > a restore into mysql. > > I don't think it's a new idea - IIRC, Aprile Pazzo did something > similar for MySQL 3 and PG 7.something. What an interesting name! I don't know much Italian other than what I've picked up from a few movies, but I think I now know what Pazzo means ... -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
>> >What will they think of next! >> >http://krow.livejournal.com/502908.html >> >I suppose it makes as much sense as the others, except why would you >> >want to use mysql if the storage is in postgres? >> >> If you've inherited data in a postgresql database this will allow >> you to migrate it to the industry standard database without the >> inconvenience and downtime of a dump from postgresql and >> a restore into mysql. >> >> I don't think it's a new idea - IIRC, Aprile Pazzo did something >> similar for MySQL 3 and PG 7.something. > > What an interesting name! I don't know much Italian other than what > I've picked up from a few movies, but I think I now know what Pazzo > means ... Yeah well you know mysqldump has an option "export to postgres syntax" so you can reimport in postgres. I encourage you to try it one day, you'll be amazed. mysqldump --password -d -u root immo_forum DROP TABLE IF EXISTS `smf_topics`; CREATE TABLE `smf_topics` ( `ID_TOPIC` mediumint(8) unsigned NOT NULL auto_increment, `isSticky` tinyint(4) NOT NULL default '0', `ID_BOARD` smallint(5) unsigned NOT NULL default '0', `ID_FIRST_MSG` int(10) unsigned NOT NULL default '0', `ID_LAST_MSG` int(10) unsigned NOT NULL default '0', `ID_MEMBER_STARTED` mediumint(8) unsigned NOT NULL default '0', `ID_MEMBER_UPDATED` mediumint(8) unsigned NOT NULL default '0', `ID_POLL` mediumint(8) unsigned NOT NULL default '0', `numReplies` int(10) unsigned NOT NULL default '0', `numViews` int(10) unsigned NOT NULL default '0', `locked` tinyint(4) NOT NULL default '0', PRIMARY KEY (`ID_TOPIC`), UNIQUE KEY `lastMessage` (`ID_LAST_MSG`,`ID_BOARD`), UNIQUE KEY `firstMessage` (`ID_FIRST_MSG`,`ID_BOARD`), UNIQUE KEY `poll` (`ID_POLL`,`ID_TOPIC`), KEY `isSticky` (`isSticky`), KEY `ID_BOARD` (`ID_BOARD`) ) ENGINE=MyISAM AUTO_INCREMENT=25 DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; mysqldump --compatible=postgres --password -d -u root immo_forum DROP TABLE IF EXISTS "smf_topics"; CREATE TABLE "smf_topics" ( "ID_TOPIC" mediumint(8) unsigned NOT NULL, "isSticky" tinyint(4) NOT NULL default '0', "ID_BOARD" smallint(5) unsigned NOT NULL default '0', "ID_FIRST_MSG" int(10) unsigned NOT NULL default '0', "ID_LAST_MSG" int(10) unsigned NOT NULL default '0', "ID_MEMBER_STARTED" mediumint(8) unsigned NOT NULL default '0', "ID_MEMBER_UPDATED" mediumint(8) unsigned NOT NULL default '0', "ID_POLL" mediumint(8) unsigned NOT NULL default '0', "numReplies" int(10) unsigned NOT NULL default '0', "numViews" int(10) unsigned NOT NULL default '0', "locked" tinyint(4) NOT NULL default '0', PRIMARY KEY ("ID_TOPIC"), UNIQUE KEY "lastMessage" ("ID_LAST_MSG","ID_BOARD"), UNIQUE KEY "firstMessage" ("ID_FIRST_MSG","ID_BOARD"), UNIQUE KEY "poll" ("ID_POLL","ID_TOPIC"), KEY "isSticky" ("isSticky"), KEY "ID_BOARD" ("ID_BOARD") ); /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; Sure looks "compatible" (but with what ?)