Am Freitag, 19. Mai 2006 02:35 schrieb Robert Treat:
> On Thursday 18 May 2006 12:38, Josh Berkus wrote:
> > Personally, I'd go after MSSQL before I bothered with MySQL. Sure,
> > let's make *migration* easier for those who wake up and smell the BS, but
> > migration can (and probably should) be one-way.
>
> If you want to get users to swtich to your software from your competitors,
> you have to eliminate barriers, and a big one for any database is getting
> locked into a specific one. People aren't going to take the time to try
> switching to postgresql if they can't easily make it back to thier former
> database. It's one of the reasons why PostgreSQL's standards compliance is
> so important; if you want to swtich to a new database, your best bet is to
> give PostgreSQL a shot, because even if you don't like it, we're not going
> to try and trap you into our software with bunches of non-standard knobs.
> Low barrier to exit == low barrier to entry.
The way to go are standards. If postgresql supports standard-sql (like we all
know it know), mysql-users has to justify their apps to use standard-sql.
What they gain is not only compatibility with PostgreSQL but compatiblity
with all database-servers, which supports this standard. They wont have much
trouble to switch back to mysql or downgrade their postgresql to oracle ;-),
if they follow standards.
Also if PostgreSQL would have a compatibility-layer, it has to follow every
quirk of mysql and will be measured by that. Much better is to promote users
of mysql to use standards.
Tommi
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
