Re: Django ORM support for NoSql databases

On Wed, Dec 18, 2013 at 4:41 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 17 déc. 2013, at 20:38, Karen Tracey wrote: > > https://groups.google.com/d/msg/django-developers/0IuJssTt8tc/TxdXQ2D0thcJ > > > Interesting. Now I remember reading that

Re: RawQuerySet as subquery when used with an __in filter

Hi all, In implementing this I ran into a bug in the way SQLite returns column information: https://code.djangoproject.com/ticket/21603 It affects raw queries in general, but this feature in particular due to the way the code generate nested SQL queries. Cheers, Alex On Friday, December

Re: Django ORM support for NoSql databases

On 17 déc. 2013, at 19:53, Javier Guerra Giraldez wrote: > On Tue, Dec 17, 2013 at 12:16 PM, Aymeric Augustin > wrote: >> Django’s ORM is entirely designed to translate between an object oriented >> API and SQL. That’s what its name says.

Re: Django ORM support for NoSql databases

On 17 déc. 2013, at 20:38, Karen Tracey wrote: > https://groups.google.com/d/msg/django-developers/0IuJssTt8tc/TxdXQ2D0thcJ Interesting. Now I remember reading that message last year. I have three reactions. First, Russell and I agree that the interest has faded.

Re: Django ORM support for NoSql databases

On Tue, Dec 17, 2013 at 12:16 PM, Aymeric Augustin wrote: > Django’s ORM is entirely designed to translate between an object oriented API > and SQL. That’s what its name says. It achieves this through roughly five > layers that bride the abstraction gap. > >

Re: Django ORM support for NoSql databases

On Tuesday, December 17, 2013 12:16:04 PM UTC-5, Aymeric Augustin wrote: > > Django’s ORM is entirely designed to translate between an object oriented > API and SQL. That’s what its name says. It achieves this through roughly > five layers that bride the abstraction gap. > > Django’s ORM is

Re: Django ORM support for NoSql databases

On Tue, Dec 17, 2013 at 2:05 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 17 déc. 2013, at 19:53, Javier Guerra Giraldez > wrote: > > > On Tue, Dec 17, 2013 at 12:16 PM, Aymeric Augustin > > wrote: > >> Django’s

Re: Django ORM support for NoSql databases

On Tue, Dec 17, 2013 at 4:50 PM, Chris Wilson wrote: > Hi all, > > > On Tue, 17 Dec 2013, Tom Evans wrote: > >> On Tue, Dec 17, 2013 at 3:35 PM, parisrocks >> wrote: >>> >>> Waiting for official Django ORM support for NoSql databases. >> >> >>

Re: Django ORM support for NoSql databases

Hi Chris, On 17 déc. 2013, at 17:50, Chris Wilson wrote: > There is no particular reason NOT to do it, unless one wants Django's ORM > layer to remain fundamentally tied to SQL. I don’t understand your sentence. To me it’s as if you were saying “there is no particular

Re: Django ORM support for NoSql databases

Hi all, On Tue, 17 Dec 2013, Tom Evans wrote: On Tue, Dec 17, 2013 at 3:35 PM, parisrocks wrote: Waiting for official Django ORM support for NoSql databases. MongoDB (and the vast majority of NoSQL databases) are not relational databases, they are document

Re: Django ORM support for NoSql databases

On Tue, Dec 17, 2013 at 3:35 PM, parisrocks wrote: > Hi Django Users, > I tried Django recently and really liked the simplistic approach for > building sites. > But there's no official support for NoSQL databases like Cassandra or > MongoDB, there's a great

Django ORM support for NoSql databases

Hi Django Users, I tried Django recently and really liked the simplistic approach for building sites. But there's no official support for NoSQL databases like Cassandra or MongoDB, there's a great community of NoSQL users waiting for an official ORM support from Django like me. I would say

Re: App-loading reloaded - apps without a models module

On 16 déc. 2013, at 12:02, Aymeric Augustin wrote: > I sent a pull request implementing my first goal: > https://github.com/django/django/pull/2076. Merged: https://github.com/django/django/compare/fe1389e911b0...4a56a93cc458 -- Aymeric. -- You