In that case the ability to support it would depend on the support in psycopg2 and how safe we consider their implementation.
Marc On 29 Jun 2015 16:01, "Collin Anderson" <cmawebs...@gmail.com> wrote: > I think XMLField was removed because the security of xml parsing and > validating is hard to get right. > > On Sunday, June 28, 2015 at 7:51:22 PM UTC-4, Russell Keith-Magee wrote: >> >> >> On Mon, Jun 29, 2015 at 7:32 AM, Josh Smeaton <josh.s...@gmail.com> >> wrote: >> >>> I'm not quite up to date on XML in databases (I've never had to use XML >>> in a database), but don't the majority of core backends support XML in some >>> way? If so, I'd probably like to see an attempt to build out XML support >>> such that all/most core databases could benefit from the new feature, >>> rather than being locked away in contrib.postgres. >>> >> >> Heh... >> >> >> https://github.com/django/django/blob/stable/1.3.x/django/db/models/fields/__init__.py#L1135 >> >> So, to answer your questions: >>> >>> Is this a project that; >>> a) would be accepted - Probably, if someone were to implement it and >>> drive it until quality was acceptable >>> b) would be fairly straight forward and - I'm not sure how >>> straightforward it would be. The addition of Lookups and Transforms will >>> help tremendously though. >>> c) would be useful to the wider community? - Not for me personally, but >>> I'm sure there'd be others that would find good use for XML support. >>> Hopefully we can get some more feedback to accurately determine that though. >>> >> >> Broadly, I agree with Josh. >> >> Given that we have contrib.postgres, we should be aiming at 100% coverage >> of PostgreSQL features in core (not saying that is possible or likely, but >> it's an aspirational goal). >> >> In cases where it is plausible to implement a feature for all backends, >> we should aim to do that. >> >> However, I don't think we should be cross platform at all costs. It would >> be possible to implement XMLField as a light layer over TextField (hey - we >> used to do exactly this), but if that's the only way to implement it, I >> don't think we should implement it at all. I'm not in favour of >> implementing known-to-be-slow design patterns for core features. Unless >> SQLite and MySQL offer a native XML data type, with reasonably rich query >> syntax, then I don't think a cross-platform is desirable. >> >> Yours, >> Russ Magee %-) >> >> -- > 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/72777a63-a357-44ba-a067-34a7a4af1b1f%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/72777a63-a357-44ba-a067-34a7a4af1b1f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/CAMwjO1ECgJ40qT-qAdzQV5vravjKduj5Aeywf6gMEsxb-tM%3D%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
