Dear knowledgeable persons: I have completed a beta-test version of a Linux remote access server for adodbapi, and have started the process if integrating them into django-mssql. (This is going to be an interesting experience for me -- I have already identified two or three new features that adodbapi needs to have.) I would like to get your collective wisdom about how to best accomplish two things.
1) The transaction logic will change drastically for django 1.6. For the supported backends it makes good sense to simply change that in the repository. However, it is reasonable to expect significant code change with the upgrade of this backend, and I think that we should maintain a single code base for a while. I was thinking of behavior similar to what I do inside of adodbapi: ...if sys.version_info >= (3,0): # note that the "if" is executed at import time, not run time. ......maxint = sys.maxsize ...else: ......maxint = sys.maxint Is there something more appropriate than django.VERSION to use for this, or is it, perhaps, just a bad idea? 2) In my unit test programs, I detect whether to use the proxy module or the regular module depending on whether their is a certain key in the connection arguments. .. import adodbapi ...import adodbapi.remote ...if "proxy_host' in connection_keywords: ......db = adodbapi.remote ...else: ......db = adodbapi ...db_connection = db.connect(connection_keywords) Would there be any technical or political reasons NOT to do that in sqlserver_ado/base.py ? -- Vernon Cole -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
