On Sun, Aug 30, 2009 at 8:52 PM, Waldemar Kornewald wrote:
>
> On Aug 28, 1:49 am, Russell Keith-Magee
> wrote:
>> To the extent that I'm in a position to provide design guidance and
>> feedback from the perspective of the Django Core, put me on this list
>> too. Time permitting, I might be able
On Mon, Aug 31, 2009 at 2:48 AM, sjtirtha wrote:
>
> Hi,
>
> I'm starting using CouchDB with Python.
> Django db models always work with Queries. I can understand this,
> because SQL is a query language.
> However, the non sql DBs do not always have the concept of queries.
> For example, in CouchD
On Mon, Aug 31, 2009 at 2:54 AM, sjtirtha wrote:
>
> Hi,
>
> From this point of view, I would propose, to make a new Model that
> supports non SQL DB.
> So developer can decide whether they want to store the object in SQL
> or in non SQL DB.
There are two problems here:
1. You want Django to be
Hi,
I'm starting using CouchDB with Python.
Django db models always work with Queries. I can understand this,
because SQL is a query language.
However, the non sql DBs do not always have the concept of queries.
For example, in CouchDB all CRUD operation is process via HTTP
request.
Create operati
Hi,
I have another requirement for non sql DB support in Django, which I
think will be very applicable.
Most of the current applications do not use 100% non sql DB for the
data storage. Most of them still mix SQL and non SQL DB as data
storage.
Because both of them should not compete against one
On Mon, Aug 3, 2009 at 11:25 PM, Luke Plant wrote:
>
> Hi all,
>
> Some big changes to the CSRF protection nearly got in to Django 1.1,
> but didn't. Since then, more work has been done, overhauling the
> whole thing really. There has been a huge amount of discussion on
> mailing lists and ticke
On Sun, Aug 30, 2009 at 11:06 AM, Waldemar
Kornewald wrote:
>
> On Aug 30, 3:50 pm, Andi Albrecht
> wrote:
>> No need to hurry. I'll keep this in sync with the trunk - should be
>> really unproblematic :)
>
> I'm not really doing this just for fun, so I'd rather get it done
> faster. ;)
>
>> Rega
On Aug 30, 3:50 pm, Andi Albrecht
wrote:
> No need to hurry. I'll keep this in sync with the trunk - should be
> really unproblematic :)
I'm not really doing this just for fun, so I'd rather get it done
faster. ;)
> Regarding the App Engine backend: I have some minimal code here for
> the datab
On Sun, Aug 30, 2009 at 2:52 PM, Waldemar Kornewald wrote:
>
> On Aug 28, 1:49 am, Russell Keith-Magee
> wrote:
>> To the extent that I'm in a position to provide design guidance and
>> feedback from the perspective of the Django Core, put me on this list
>> too. Time permitting, I might be able
On Aug 28, 1:49 am, Russell Keith-Magee
wrote:
> To the extent that I'm in a position to provide design guidance and
> feedback from the perspective of the Django Core, put me on this list
> too. Time permitting, I might be able to contribute some code, too.
Awesome. Could you please provide som
Please don't crosspost to both django-users and django-developers. Pick the
right list and post there, in this case -users.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
On Aug 29, 8:34 pm, Mike Malone wrote:
> > Do you also intend to contribute some code? You could team up with
> > Mitch on the SimpleDB backend, for example (at least, you seemed to be
> > most interested in that).
>
> Sure.
Great! :)
> [...] I'm afraid that
> emulating the SQL join syntax in g
For example, I need a view function to do this.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from
13 matches
Mail list logo
