Daniel C. wrote: > I'm worried that MS won't scale very well. (Plus I like Postgres > better. But our DBA likes MS SQL better.)
In my experience, whatever the dba wants to use, you'll end up using it. On the other hand, if the dba is good enough it won't really make a difference. Just demand that he be the one to optimize your queries once they work. > I'm also going to recommend moving to Django from PHP, which would > make Postgres the natural option. That requires a move to Python from PHP as well. From personal experience, moving from one language to another is very unproductive. If you're willing or able to allocate the right amount of time (quadruple your worst case estimate is a good starting point) you *mihgt* be able to pull it off. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
