in reply to Drowning in Modules - Suggest those for DB App

To be honest if you are going to use MS SQL from the outset then I really wouldn't bother worrying about moving to MySQL or PostgresSQL later if you are planning on staying on a windows platform - it is debatable whether the former has even some of the functionality that MS SQL has and the only major advantage PostgresSQL has (beyond the cost) that I can think of is the ability to write 'stored procedures' in multiple languages.

/J\

  • Comment on Re: Drowning in Modules - Suggest those for DB App

Replies are listed 'Best First'.
Re^2: Drowning in Modules - Suggest those for DB App
by dragonchild (Archbishop) on Oct 12, 2004 at 14:35 UTC
    Yes, MySQL 3.x and 4.x lack support for stored procedures and triggers (which are really just a special case of stored procedures). However, MySQL 5.x (currently under development) will have complete support for stored procedures, triggers, and updateable views. In addition, NDB will be out soon, providing true clustering and failover. Plus, with MySQL 4.1.x, you get the ability to have an embedded server, if that's important to you.

    So, converting to MySQL now will allow a more robust upgrade path than any other database I know of, other than Oracle and, possibly, Sybase.

    Being right, does not endow the right to be rude; politeness costs nothing.
    Being unknowing, is not the same as being stupid.
    Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
    Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.