Hi Riccardo,
> I recently put some spare time on the same problem, trying to extend
> the django database API to support the management of chemical
> information.
Sweet!
I must say that I looked at the code with some dismay. Not because of
the code, but because it looks like it's a *lot* of work to handle
UDFs. I had hoped it would be much easier.
> Depending on your plans, it
> would be interesting if we could collaborate on this.
A quick look at the implementation tells me it would take me a couple
of days to get up to speed and understand how the parts go together.
I'm doing this work for a paying client, and I have a solution with
raw(). We know already that the raw search doesn't do the right thing
for the general case, eg, it doesn't work with our pagination code.
So I can see that after we have deployed (which will be next month)
and after I go to conferences (ICCE and EuroPython) in June, then it
might be something I'll be able to work on, and perhaps even get
funding to work on.
So yes, I'm interested (though I would implement a comparable OEChem
back-end), but no, it's not going to be in the next few months.
Cheers!
Andrew
da...@dalkescientific.com
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
