
When Unix, Linux or BSD variants come to par for the other things I do than it’s even easier to switch. If I can develop on Windows with all these benefits and it works on UNIX,Linux,BSD or whatever else then I am far further ahead. UNIX,Linux,BSD don’t fill some of those markets. I want to be 100% compatible with my work environment. I want to be able to do everything that I do in my regular every day life.
I don’t want to have to run some UNIX, Linux or BSD variant to develop for MySQL, Postgres, Apache or any other popular package.

I for one am glad these apps are available on Windows. I know MysSQL has progressed much, but last time I checked (last summer) it was still far behind in ease of use for someone used to “traditionnal” databases.Īnyway native Windows support for Pg is great news and most the changelog is very promising (changing row type with ALTER TABLE and TABLESPACE support have been long awaited features). And, to my surprise, it has sometime been quicker than a more “orthodox” database use.
Lovechoice switch code#
With Pg migration was mostly a rewrite of Oracle specific type and porting some PL/SQL.īut, I’ve found that for developpers that tend to be less database oriented in their background find often easier to write and maintain code that heavily loops into simple MySQL results. It proved to be very scalable and even quicker than Oracle on some heavy processing.įor us, MySQL would have required that we implement in client code many of the constrainst and features that would have to be implemented in some scripts used for batch work, web front end and a few fat clients. After a month of trial, we moved to PgSQL that provided us with a very stable, standard implementation.

This policy of empty results instead of error messages was very annoying. Trying to make things work on MySQL has been a huge pain, complex queries where returning empty results because they where using to many joins or non supported SQL dialect.
Lovechoice switch free#
Then in 2000/2001 I had to migrate some applications from Oracle to any free database that would not oblige us to pay tons of money to Oracle for secondary functions. Of course having a database that enforce relational rules is a great help when designing applications in this traditionnal way. Just as an exemple of why one may choose PgSQL over MySQL, my experience have been quite educative.Ĭoming from an Oracle background(in telecom world), I’ve long been used to design table/constraints and all the entity/relation and Codd stuff before creating any table.įrom there views, requests … then code and generaly a few helping additionnal request/table/views and a few stored procedure to optimise a few tasks(mostly triggers).
