Russ: I am not entirely sure what I am asking, either, but your answer has already helped. Indeed, PEP 249 is silent about support of UUID feilds, because it was written too long ago. It is also silent about support of decimal and datetime fields for the same reason. You have just taught me why we (meaning myself and other db-api authors) need a new, updated PEP.
As for "whoever is responsible" -- that's me! I am the guy who maintains the Python ADO module. I am in the middle of an effort to upgrade that module specifically for django's benefit. My problem is that I have so little experience as a _user_ of django that I'm not a good judge of what we (meaning other django users) really need. I feel like a guy who doesn't know how to drive designing a new car. That's why I am asking so many off-the-wall questions to this group. I need someone to say: "No, we really need the steering wheel to stay where it is... Now if you can do something about needing one foot for the gas, and one foot for the brake, and one foot for the clutch in order to start on a hill -- we could really use THAT," So, if I were to add direct UUID support to adodbapi, it might eventually get included in a new PEP, and eventually picked up by the likes of psycopg. No guarantees, but it would be a start. My present project is to make a way for Linux users to have a door into ADO. That ought to help to gain some traction for django-mssql, which is why I am here. I have been seeing a use for this for ages -- but am now working for a company who needs to have the feature working -- about three weeks ago. If I mention that the UUID field I am working with happens to be in a record of collected data points which I also need to put on a map in geo-django, which does not work with django-mssql (yet, and I am still learning geo-django) you have an idea why I need wise advice whenever I can get it. Thank you. You are helping eHealth Africa to put an end to polio. So -- is it worth my time to muck with direct database api support of uuid fields? Where am I in relation to: "Now is better than never. Although never is often better than *right* now."? -- Vernon -- 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.
