Jakub Labath wrote:
Hi Joshua,Eugene,
Joshua, you are of course right. At the same time when there is
someone like me trying to replace existing solutions in place (which
are all under IIS and MSSQL). Declaring one day company-wide switch
to a different SQL server, different operating system and different
framework/language, well that takes more courage than I have :-). I
much prefer to go easy on it and first give everybody chance to see
why django is great. Therefore MSSQL and IIS support is important to
me.
I understand your point. I have certain luxuries that others don't and
I have longed to find a decent toolkit that supports PostgreSQL *first*.
Django appears to do that, so when people start talking about making
it work with others, I get a little nervous. Although I will say that
at least it is MS SQL and not MySQL.
Now having said that there is no reason why the core developers should
worry about it. I need it and I should help to build it.
Now that is a refreshing statement to read.
The MSSQL support seems to be most pressing to me. Anybody else interested?
I would suggest focusing on ODBC support, not MSSQL support. That way in
general, the work that you will do will work for everyone and you may
more easily get a community to support you.
Sincerely,
Joshua D. Drake
j
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
