Good idea. Let INSTALLED_APPS be iterable, and let Django deployment
do its job based on the configuration. Little to say though:
INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.admin',
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 Thu, Apr 8, 2010 at 2:56 PM, Dagvadorj Galbadrakh
wrote:
> Good idea. Let INSTALLED_APPS be iterable, and let Django deployment
> do its job based on the configuration. Little to say though:
>
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.cont
Thanks for review.
On Thu, Apr 8, 2010 at 3:15 PM, burc...@gmail.com wrote:
>
> May I have few questions.
> 1) And what if foo.gsoc has taiwan submodule already?
There will be certain conventions on which names not to use as an
instance name such as, views, models, etc. Plus, Django can check if
On Thu, Apr 8, 2010 at 3:27 PM, Dagvadorj Galbadrakh
wrote:
> Thanks for review.
>
> On Thu, Apr 8, 2010 at 3:15 PM, burc...@gmail.com wrote:
>>
>> May I have few questions.
>> 1) And what if foo.gsoc has taiwan submodule already?
>
> There will be certain conventions on which names not to use as
Thanks for the brilliant advice. I will do so and am now. :)
On Thu, Apr 8, 2010 at 6:09 PM, burc...@gmail.com wrote:
> On Thu, Apr 8, 2010 at 3:27 PM, Dagvadorj Galbadrakh
> wrote:
>> Thanks for review.
>>
>> On Thu, Apr 8, 2010 at 3:15 PM, burc...@gmail.com wrote:
>>>
>>> May I have few quest
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
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
An App Loading mechanism for Django
About Me
--
Hi everyone,
My name is Nick Sandford, I'm an electrical engineering student at the
University of Western Australia.
Background
---
I haven't been a particularly active contributor to any open s
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 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 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 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
Hi Nick,
I don't like your application creation syntax (why using dict-based
DSL instead of class-based?), but
I like how you approach the overall problem.
More than that, you have shown you do understand all the problems
you're going to solve, and that you have design skills required for
solution
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 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
On Apr 8, 5:33 pm, Nick Sandford wrote:
> An App Loading mechanism for Django
>
>
> About Me
> --
> Hi everyone,
>
> My name is Nick Sandford, I'm an electrical engineering student at the
> University of Western Australia.
>
> Background
> ---
On Fri, Apr 9, 2010 at 3:41 AM, burc...@gmail.com wrote:
>
> Hi Nick,
>
> I don't like your application creation syntax (why using dict-based
> DSL instead of class-based?), but
> I like how you approach the overall problem.
> More than that, you have shown you do understand all the problems
> you
On Fri, Apr 9, 2010 at 5:21 AM, Vinay Sajip wrote:
>
>
> Have you looked at the patch on ticket 3591 which does some of this
> already? Would you be using it as a starting point?
It's a great place to start, and gives a good idea about where to look for
problems. I'm not sure about get_installed_
I've written an application to improve Django's Test Suite.
http://code.djangoproject.com/wiki/SummerOfCode2010#Testingupdates
My application is here (also pasted below for convenience):
http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/paulmcmillan/t127077396156
I'm hoping fo
20 matches
Mail list logo
