Home Original page

mx odbc

Kim Petersen kp at kyborg.dk
Wed Jul 9 04:12:29 EDT 2003 
M.-A. Lemburg wrote:
> Kim Petersen wrote:
> 
>> Regarding ODBC usage in Python...
>>
>> it seems to me that there is a couple of ways to use odbc from python,
>> one of these is the MX version - now that one has a pretty steep 
>> licence cost (imho). So now comes my question (from reading this group 
>> quite a bit):
>>
>>     - what is the basic reason for using MX versus the others?
> 
> 
> Having a maintained and actively supported ODBC interface which
> works on all major platforms, not just Windows ?!

I'm not arguing that thats not important - *but* paying 70$ pr. 
customer, is the equivalent of paying you for 1hr of support for each 
customer [not installation mind you], where our own licence/supportcost 
is already getting lower and lower... I find that _extremely_ steep - i 
could and would accept such a cost for the python platform (no trouble!) 
[except in the few (from our view) cases where the user just needs a 
small tool.

IMHO your setting the value of the package so high, that there would be 
better economics in making a rewrite of our database modules every time 
a customer needs some new one (porting to a new database specific DB-SIG 
compliant module).

>
More information about the Python-list mailing list