The meta API used by admin and model forms should be completely public and stable. The problem is that some methods of the meta API return field instances, and the API for the fields (especially for related fields) isn't public nor stable. You'll need to somehow return field instance that act like Django's.
- Anssi On Thu, Sep 17, 2015 at 7:00 AM, Asif Saifuddin <auv...@gmail.com> wrote: > Hi, > > With "support" I meant having a official djangoish way to use sqlalchemy on > django. As I have to use model meta API to add support for any non django > backend to orm my question is, is django meta API fully formalized? If not > how much work is needed to formalize them?(as denial did a lots of work then > their should be proper guideline or enough insight to start digging? ) > > Or we are ok with the existing API's? > > Regards > > Asif > > On Thu, Sep 17, 2015 at 5:20 AM, Russell Keith-Magee > <russ...@keith-magee.com> wrote: >> >> Hi Asif, >> >> It depends entirely what you mean by "support". >> >> Django is just Python, so there's absolutely no reason you can't write >> a Django site that uses Django for the URLs, views and forms, but >> SQLAlchemy for the data access. >> >> Out of the box, you won't be able to use ModelForms or the Admin. >> However, with the new stable Meta API that was added in 1.8, you >> should be able to write a layer for SQLAlchemy that makes a SQLAlchemy >> table definition "quack" like a Django model, allowing you to wrap. >> >> Daniel Parathion did this as a proof of concept as part of his GSoC >> project using the Gmail API - he was able to expose a Gmail inbox as a >> Django model, browse his inbox in Admin, and use a ModelForm to >> compose an email from within the admin. >> >> I gave a presentation at the recent DjangoCon US about this topic; the >> slides are available here: >> >> https://speakerdeck.com/freakboy3742/i-never-meta-model-i-didnt-like >> >> Video should be available in the next week or so. Short version: it >> won't be *trivial*, but it's certainly *possible*, although you're in >> undocumented territory, so you'll have to navigate the sharp edges >> yourself. >> >> Yours, >> Russ Magee %-) >> >> >> >> >> On Wed, Sep 16, 2015 at 4:35 PM, Asif Saifuddin <auv...@gmail.com> wrote: >> > Hi, >> > >> > >> > How much difficult it will be to add SQLalchemy support to django? what >> > are >> > the technical difficulties? And which are the ways to add sqlalchemy >> > support >> > to django? >> > >> > As SQLalchemy is separated in core and orm will it be wise to use >> > sqlalchemy >> > core as the backend for django orm? Or through the meta api? any >> > suggestion >> > or direction to the solutions? >> > >> > The available 3rd party packages seems to be incomplete. >> > >> > >> > Regards >> > >> > Asif >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Django developers (Contributions to Django itself)" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to django-developers+unsubscr...@googlegroups.com. >> > To post to this group, send email to django-developers@googlegroups.com. >> > Visit this group at http://groups.google.com/group/django-developers. >> > To view this discussion on the web visit >> > >> > https://groups.google.com/d/msgid/django-developers/33078771-6802-44f9-9182-1eb2f7104e23%40googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/django-developers/puVGMV7GlNE/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAJxq849Ccd%2Bvz9uYf45UtcjnMXToRChoO-MyTz5b3YLFFEp6Ww%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAKAqTgrgsSz6OEWQXt5LzLVOCybsLyV1yZJV%3DrPBbVHu6D9xKA%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALMtK1GemtgA4zkkKQDy7DLUjGfGfawnA4N9MgpXcXdXcESVuw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
