>Not at the moment. There are two problems that need solving here (I've
>mentioned this before either on this list or django-dev) and they're
>both still on my endless TODO list. I'll get to them one day.
>  
>
I bet your todo list looks like mine 8)
>(1) For fields that are Python wrappers over existing database fields,
>there is a small change that needs to be made to the model attribute
>creation so that the data from the database is passed to the Field
>sub-class's constructor for converting into the right type. This change
>is relatively simple (about two lines of code).
>  
>
I may take a look at this....

>        An example of this is if you make a field called Sudoku, say,
>        but the data is stored as a string of 81 characters in the
>        database. After retrieving the data, it would be nice if the
>        model attribute was actually a Sudoku class instance, rather
>        than a seemingly opaque string.
>  
>
...because it would solve a lot of my problem. In my case, I could call 
the function to transform the database's geometry object into something 
the user can use and understand

>(2) For fields that are new database types, it is slightly more fiddly.
>We need a way to have them created correctly in the database (possibly
>also adding introspection, on the "give an inch and somebody is going to
>complain about the rest of the mile being missing" principle). We
>possibly need a retrieval mapping function -- imagine if we didn't have
>a native date field; how might we implement it as a third-party class --
>or possibly just hand off the rest of the work to case (1).
>
>  
>
In my case, I don't think I could need this if I had (1). Saving the 
data isn't my real problem, it's getting it out into a useful format

thanks for the info
--B


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to