On Apr 9, 9:06 am, Russell Keith-Magee wrote:
> No - Array types aren't available everywhere. However, it would be
> nice to be able to support them (even if not in core); if this GSoC
> lays the groundwork to make this possible, then it's worth looking at.
We already implemented a ListField in d
On Thu, Apr 8, 2010 at 11:03 PM, flo...@gmail.com wrote:
> On Apr 8, 12:32 pm, Waldemar Kornewald wrote:
>
>> What I'm proposing is not a complete emulation of all features at all
>> cost, but simply an automation of the things that are possible and in
>> wide use on nonrel DBs. Moreover, you'd o
On Thu, Apr 8, 2010 at 5:55 AM, Waldemar Kornewald wrote:
> On Wed, Apr 7, 2010 at 5:22 PM, Alex Gaynor wrote:
>>> Other issues that spring to mind:
>>>
>>> * What about nonSQL datatypes? List/Set types are a common feature of
>>> Non-SQL backends, and are The Right Way to solve a whole bunch of
On Apr 8, 12:32 pm, Waldemar Kornewald wrote:
> What I'm proposing is not a complete emulation of all features at all
> cost, but simply an automation of the things that are possible and in
> wide use on nonrel DBs. Moreover, you'd only use these features where
> actually needed, so this would be
Hi Waldemar, Alex,
why you didn't do different threads for the different issues? :\
Regarding getting .filter() to work, I suggest we will use explicit
and implicit indexes, something like this:
class User(models.Model):
username = models.CharField(max_length=200, db_index=True) #
db_index=Tr
On Thursday, April 8, 2010, flo...@gmail.com wrote:
> On Apr 8, 10:50 am, Javier Guerra Giraldez wrote:
>
>> A: use the _same_ ORM with NoSQL backends. then it's important to
>> provide (almos) every capability of the current ORM, even if they have
>> to be emulated when the backend doesn't prov
On Apr 8, 10:50 am, Javier Guerra Giraldez wrote:
> A: use the _same_ ORM with NoSQL backends. then it's important to
> provide (almos) every capability of the current ORM, even if they have
> to be emulated when the backend doesn't provide it natively.
To do this would mean to essentially impl
On Thu, Apr 8, 2010 at 12:08 PM, Waldemar Kornewald
wrote:
>> No, we don't. People are desiging there data in ways that fit their
>> datastore. If all people did was implement a relational model in
>> userland code on top of non-relational databases then they'd really be
>> missing the point.
>
>
On Thu, Apr 8, 2010 at 6:14 PM, Alex Gaynor wrote:
> On Wed, Apr 7, 2010 at 4:43 PM, Waldemar Kornewald
> wrote:
>> On Wed, Apr 7, 2010 at 5:12 PM, Alex Gaynor wrote:
>>> No. I am vehemently opposed to attempting to extensively emulate the
>>> features of a relational database in a non-relatio
On Wed, Apr 7, 2010 at 5:55 PM, Waldemar Kornewald wrote:
> On Wed, Apr 7, 2010 at 5:22 PM, Alex Gaynor wrote:
>>> Other issues that spring to mind:
>>>
>>> * What about nonSQL datatypes? List/Set types are a common feature of
>>> Non-SQL backends, and are The Right Way to solve a whole bunch of
On Wed, Apr 7, 2010 at 4:43 PM, Waldemar Kornewald wrote:
> On Wed, Apr 7, 2010 at 5:12 PM, Alex Gaynor wrote:
>> No. I am vehemently opposed to attempting to extensively emulate the
>> features of a relational database in a non-relational one. People
>> talk about the "object relational" imped
Hi all,
On Thu, Apr 8, 2010 at 12:55 AM, Waldemar Kornewald
wrote:
> On Wed, Apr 7, 2010 at 5:22 PM, Alex Gaynor wrote:
>>> Other issues that spring to mind:
[...]
> Well, you might be able to quickly adapt the MongoDB backend to GAE
> (within GSoC time constraints) due to their similarity. Anyw
On Wed, Apr 7, 2010 at 5:22 PM, Alex Gaynor wrote:
>> Other issues that spring to mind:
>>
>> * What about nonSQL datatypes? List/Set types are a common feature of
>> Non-SQL backends, and are The Right Way to solve a whole bunch of
>> problems. How do you propose to approach these datatypes? Wha
On Wed, Apr 7, 2010 at 5:12 PM, Alex Gaynor wrote:
> No. I am vehemently opposed to attempting to extensively emulate the
> features of a relational database in a non-relational one. People
> talk about the "object relational" impedance mismatch, much less the
> "object-relational non-relational
On Wed, Apr 7, 2010 at 2:19 PM, lasizoillo wrote:
> 2010/4/7 Alex Gaynor :
>
>> * 2 weeks - begin working on a backend for a non-relational database
>> (probably
>> MongoDB)
>
> Pymodels[1] have backends for MogoDB and Tokyo Tyrant/Cabinet. Maybe
> some things can be reused in backend.
>
> htt
2010/4/7 Alex Gaynor :
> * 2 weeks - begin working on a backend for a non-relational database
> (probably
> MongoDB)
Pymodels[1] have backends for MogoDB and Tokyo Tyrant/Cabinet. Maybe
some things can be reused in backend.
http://bitbucket.org/neithere/pymodels/
Regards,
Javi
--
You rec
On Wed, Apr 7, 2010 at 6:47 AM, Russell Keith-Magee
wrote:
> On Wed, Apr 7, 2010 at 8:11 AM, Alex Gaynor wrote:
>> Non-relational database support for the Django ORM
>> ==
>>
>> Note: I am withdrawing my proposal on template compilation. Another s
On Wed, Apr 7, 2010 at 4:43 AM, Waldemar Kornewald wrote:
> Hey Alex,
>
> On Apr 7, 2:11 am, Alex Gaynor wrote:
>> Non-relational database support for the Django ORM
>> ==
>>
>> Note: I am withdrawing my proposal on template compilation. Another
>
On Wed, Apr 7, 2010 at 8:11 AM, Alex Gaynor wrote:
> Non-relational database support for the Django ORM
> ==
>
> Note: I am withdrawing my proposal on template compilation. Another student
> has expressed some interest in working on it, and in any
Hey Alex,
On Apr 7, 2:11 am, Alex Gaynor wrote:
> Non-relational database support for the Django ORM
> ==
>
> Note: I am withdrawing my proposal on template compilation. Another
> student
> has expressed some interest in working on it, and in any
Non-relational database support for the Django ORM
==
Note: I am withdrawing my proposal on template compilation. Another student
has expressed some interest in working on it, and in any event I am now more
interested in working on this project.
A
21 matches
Mail list logo
