On Thu, Dec 19, 2013 at 1:47 AM, Javier Guerra Giraldez
wrote:
> On Wed, Dec 18, 2013 at 12:18 PM,
> wrote:
> >
> > Wouldn't an easy (i.e. straightforward) solution be to add an Django
> "ODM"
> > that mirrors the ORM wherever it makes
On Thu, Dec 19, 2013 at 1:18 AM, wrote:
>
>
> On Tuesday, December 17, 2013 8:12:43 PM UTC-6, Russell Keith-Magee wrote:
>>
>>
>> My claim is that complete abstraction of the data store shouldn't be the
>> goal. What we should be aiming for is sufficient API
On Wed, Dec 18, 2013 at 12:18 PM, wrote:
>
> Wouldn't an easy (i.e. straightforward) solution be to add an Django "ODM"
> that mirrors the ORM wherever it makes sense? This sounds pretty close to
> your second solution, except choosing SQL vs NoSQL means
On Tuesday, December 17, 2013 8:12:43 PM UTC-6, Russell Keith-Magee wrote:
>
>
> My claim is that complete abstraction of the data store shouldn't be the
> goal. What we should be aiming for is sufficient API compatibility to allow
> for two things:
>
> * ModelForms wrapping a model from a
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
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.
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.
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.
>
>
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
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
On Tue, Dec 17, 2013 at 4:50 PM, Chris Wilson <ch...@aptivate.org> wrote:
> Hi all,
>
>
> On Tue, 17 Dec 2013, Tom Evans wrote:
>
>> On Tue, Dec 17, 2013 at 3:35 PM, parisrocks
>> <saravanan.sellathu...@gmail.com> wrote:
>>>
>>> Wa
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
Hi all,
On Tue, 17 Dec 2013, Tom Evans wrote:
On Tue, Dec 17, 2013 at 3:35 PM, parisrocks
<saravanan.sellathu...@gmail.com> wrote:
Waiting for official Django ORM support for NoSql databases.
MongoDB (and the vast majority of NoSQL databases) are not relational
databases, they are do
goDB, there's a great community of NoSQL users waiting for an official
> ORM support from Django like me. I would say Django with NoSQL ORM support
> could actually make it more popular compared to its rivals Ruby on Rails or
> even Java for that reason.
>
> Waiting for official Dj
Django with NoSQL ORM support
could actually make it more popular compared to its rivals Ruby on Rails or
even Java for that reason.
Waiting for official Django ORM support for NoSql databases.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Django devel
15 matches
Mail list logo