At 11:54 AM -0700 9/5/07, laurel wrote: >One issue that we ran into at ATRC which required a move from MYSQL to >PostgreSQL on one webapp was the issue of standards compliance. There >were queries that we just couldn't do efficiently in mysql which were >possible in postgresql. This aspect might be worth looking into too.
Without specifics it's hard to evaluate. I'd argue strongly that the portal code should work fine with a wide variety of databases. One advantage PostgreSQL has in agile development however is that changes to schemas can be put in a transaction. I use scripts all the time to update the schemas I use. Mostly I am adding new models -- but in refactoring I sometimes want to change the name of a table or column, etc. Using Mysql if there is a problem with my syntax etc it bombs in the middle of the change and I have to back it out manually. PostgreSQL will rollback the whole change that was scoped by the transaction. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
