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,
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
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
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
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
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
>
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
>
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,
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
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
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 find a little introduction
to the code here:
Hey,
a little status update:
We've switched our work to Alex' github multi-db branch because we
depend on that to make a clean non-relational backend API. Otherwise
we'd have to rewrite too much code once multi-db gets merged into
trunk. The new branch is at:
On Thu, Oct 29, 2009 at 9:51 PM, Alex Gaynor wrote:
> I haven't had a chance to look at it, and I probably won't until at
> least a few of the items on my plate are dealt with. That being said
> I am extremely leery about investing time in something with names like
>
On Thu, Oct 29, 2009 at 2:44 PM, Waldemar Kornewald
wrote:
>
> Hi,
> Russell and Alex, did you already look at QueryGlue? We really need to
> discuss which branch the new query_class() should be in.
>
> Bye,
> Waldemar Kornewald
>
> >
>
I haven't had a chance to look at
Hi,
Russell and Alex, did you already look at QueryGlue? We really need to
discuss which branch the new query_class() should be in.
Bye,
Waldemar Kornewald
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
On Mon, Oct 26, 2009 at 3:05 PM, Russell Keith-Magee
wrote:
>
> On Mon, Oct 26, 2009 at 8:46 PM, Waldemar Kornewald
> wrote:
>>
>> On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
>> wrote:
>>> To date, sql.Query is the
On Mon, Oct 26, 2009 at 8:46 PM, Waldemar Kornewald
wrote:
>
> On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
> wrote:
>> To date, sql.Query is the right structure for all Django's supported
>> backends. It might even be the right structure
On Mon, Oct 26, 2009 at 1:12 PM, Russell Keith-Magee
wrote:
> To date, sql.Query is the right structure for all Django's supported
> backends. It might even be the right structure for a non-SQL backend
> that provides a SQL-like query layer (AppEngine possibly falls into
On Mon, Oct 26, 2009 at 4:52 PM, Waldemar Kornewald
wrote:
>
> On Mon, Oct 26, 2009 at 1:46 AM, Russell Keith-Magee
> wrote:
>> The current query_class will need to change slightly to support
>> multi-db, so anything you implement against that
On Mon, Oct 26, 2009 at 1:46 AM, Russell Keith-Magee
wrote:
> The current query_class will need to change slightly to support
> multi-db, so anything you implement against that interface will
> require some rework later on. That said, the fundamental approach
> (i.e., the
On Mon, Oct 26, 2009 at 12:42 AM, Thomas Wanschik
wrote:
>
>
>
> On 22 Okt., 23:52, Russell Keith-Magee wrote:
>> On Fri, Oct 23, 2009 at 5:09 AM, Thomas Wanschik
>>
>> wrote:
>>
>> >> When a new QuerySet is
On 22 Okt., 23:52, Russell Keith-Magee wrote:
> On Fri, Oct 23, 2009 at 5:09 AM, Thomas Wanschik
>
> wrote:
>
> >> When a new QuerySet is instantiated (e.g. by calling
> >> Model.objects.all()) it asks the backend for its Query class and then
I just want to remind contributers to fill in the cell "Assigned to"
and "Status" in the task spreadsheet while working on a specific task
in order to prefend problems.
Here is the link:
https://spreadsheets.google.com/ccc?key=0AnLqunL-SCJJdE1fM0NzY1JQTXJuZGdEa0huODVfRHc=en
Bye,
Thomas Wanschik
On Fri, Oct 23, 2009 at 5:09 AM, Thomas Wanschik
wrote:
>
>> When a new QuerySet is instantiated (e.g. by calling
>> Model.objects.all()) it asks the backend for its Query class and then
>> creates an instance of that class. By default, this class is
>> sql.Query. Only
http://code.google.com/p/live-android/
On 22 Okt., 13:35, Waldemar Kornewald wrote:
> Hi everyone,
> this rather long mail contains a status report and instructions for
> contributors and implementation notes for Django core developers. If
> you only want to know the
On Thu, Oct 22, 2009 at 2:07 PM, Russell Keith-Magee
wrote:
>
> On Thu, Oct 22, 2009 at 7:46 PM, Waldemar Kornewald
> wrote:
>>
>> Hi again,
>> now a little question:
>>
>> Some fields do type conversions. For example, TimeField converts
>> datetime
On Thu, Oct 22, 2009 at 2:07 PM, Russell Keith-Magee
wrote:
>
> On Thu, Oct 22, 2009 at 7:46 PM, Waldemar Kornewald
> wrote:
>>
>> Hi again,
>> now a little question:
>>
>> Some fields do type conversions. For example, TimeField converts
>> datetime
On Thu, Oct 22, 2009 at 7:46 PM, Waldemar Kornewald
wrote:
>
> Hi again,
> now a little question:
>
> Some fields do type conversions. For example, TimeField converts
> datetime objects into time objects.
> App Engine doesn't support time, but only datetime, so should we do
Hi again,
now a little question:
Some fields do type conversions. For example, TimeField converts
datetime objects into time objects.
App Engine doesn't support time, but only datetime, so should we do
such conversions at the backend level or should we expect the field to
handle it (esp. if it
Hi everyone,
this rather long mail contains a status report and instructions for
contributors and implementation notes for Django core developers. If
you only want to know the status you can stop after the first section.
If you want to contribute I hope this provides a good starting point
into our
30 matches
Mail list logo