On Sun, Jan 17, 2010 at 9:56 PM, Waldemar Kornewald
wrote:
> On Sun, Jan 17, 2010 at 5:36 AM, Russell Keith-Magee
> wrote:
>> On Sun, Jan 17, 2010 at 9:37 AM, Waldemar Kornewald
>> wrote:
>>> On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com wrote:
I'm not really a developer on Django its
On Sun, Jan 17, 2010 at 5:36 AM, Russell Keith-Magee
wrote:
> On Sun, Jan 17, 2010 at 9:37 AM, Waldemar Kornewald
> wrote:
>> On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com wrote:
>>> I'm not really a developer on Django itself, but I am fairly
>>> interested in non-relational databases, and
On 17 Jan., 05:36, Russell Keith-Magee wrote:
> On Sun, Jan 17, 2010 at 9:37 AM, Waldemar Kornewald
>
> wrote:
> > On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com wrote:
> >> I'm not really a developer on Django itself, but I am fairly
> >> interested in non-relational databases, and some o
On Sun, Jan 17, 2010 at 9:37 AM, Waldemar Kornewald
wrote:
> On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com wrote:
>> I'm not really a developer on Django itself, but I am fairly
>> interested in non-relational databases, and some of the things being
>> said in this thread worry me a bit.
>
>
On Sat, Jan 16, 2010 at 10:35 PM, flo...@gmail.com wrote:
> I'm not really a developer on Django itself, but I am fairly
> interested in non-relational databases, and some of the things being
> said in this thread worry me a bit.
OK, if you read my mail literally I sound like "all" nonrel DBs are
I'm not really a developer on Django itself, but I am fairly
interested in non-relational databases, and some of the things being
said in this thread worry me a bit.
> 1. Nonrel DBs don't distinguish between INSERT and UPDATE
> On such DBs Model.save_base() shouldn't check if an entity already
> e
On Fri, Jan 15, 2010 at 3:55 AM, Russell Keith-Magee
wrote:
> And to be clear - a solid proposal isn't just "merge this branch". A
> patch/branch is one way to prove that you have thought about the
> problem in detail, but you also need to provide the discussion and
> description necessary to expl
On Fri, Jan 15, 2010 at 5:08 AM, Waldemar Kornewald
wrote:
> On Thu, Jan 14, 2010 at 2:42 PM, Russell Keith-Magee
> wrote:
>> Speaking for myself, I'm pretty busy trying to get features completed
>> before the 1.2 feature deadline. At the moment, anything that isn't on
>> the 1.2 roadmap is only
On Thu, Jan 14, 2010 at 2:42 PM, Russell Keith-Magee
wrote:
> Speaking for myself, I'm pretty busy trying to get features completed
> before the 1.2 feature deadline. At the moment, anything that isn't on
> the 1.2 roadmap is only getting cursory attention from me. I suspect
> the same is true of
On Thu, Jan 14, 2010 at 9:01 PM, Thomas Wanschik
wrote:
>
> On Jan 8, 1:10 pm, Waldemar Kornewald wrote:
>> Hi,
>> our non-relational port has come to the point where we need to
>> back-port the SQL layer to the query backend API (i.e., the new
>> query_class()). We could need some help from Djan
On Jan 8, 1:10 pm, Waldemar Kornewald wrote:
> Hi,
> our non-relational port has come to the point where we need to
> back-port the SQL layer to the query backend API (i.e., the new
> query_class()). We could need some help from Django developers who
> know the ORM internals really well. You can
11 matches
Mail list logo
