Re: Django Oracle backend vs. numbers
On 22 syys, 23:34, Shai Berger wrote: > On Wednesday 05 September 2012, Ian Kelly wrote: > > > > > Thanks for tracking that down. _rowfactory was a module-level > > function rather than a method, and I should have left it that way. > > So -- Ian, Anssi, are you going to include the fix in Django 1.5? I can help > by > either reviewing it for you or providing the patch for you to review. > > If you let me write the patch, I will also include the extra setting in the > "options" dictionary (choosing if expressions should be treated as decimals or > floats). I think this is then an added feature, and needs to get in before the > feature freeze. Otherwise, just fixing the performance can be treated as a bug > in be included later. Is this guess correct? Yes, the optimization part can get in after feature freeze. Applying it even at relatively late stage to 1.5 sounds OK to me. There isn't much time to do feature additions. It is possible to get the feature into 1.5, but you should not expect it to happen. As for the feature itself, I am not yet sure if it is a good idea or not. The basic problem is granularity: wouldn't you want to do this per query, or even per expression basis? Of the wording "if you let me write the patch" - of course you can write a patch. Even if somebody else claims to be working on this, you can still write a competing patch. It is not advisable as work is likely going to be wasted, but you can do it. Doing final polish for Ian's patch and providing benchmark results for it will get this patch closer to commit. If you decide to work on this, please split the patch into two: one for the ._rowfactory change, one for the feature addition. My belief is that the ._rowfactory change is going to be something we can very easily justify committing into 1.5, but the proposed feature addition sounds like something which isn't as obvious. I am ready to review patches related to this issue, but otherwise I don't have any plans to work on this. I hope Ian has some time available for this feature, as he knows a lot more about Oracle than I do. - Anssi -- 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 this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Create a new Django object with 'using' kyword in multi database application
Hi,
Thanks for suggestion Aymeric, I'll visit Django-users.
Thanks
Laxmikant
On Fri, Sep 21, 2012 at 6:55 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hi Laxmikant,
>
> This is a question is about using Django; please post such questions
> to django-users.
>
> The topic of django-developers is the development of Django itself.
>
> Thanks!
>
> --
> Aymeric.
>
> PS: look at database-level replication.
>
>
>
> Le 21 sept. 2012 à 09:11, Laxmikant Gurnalkar <
> laxmikant.gurnal...@gmail.com> a écrit :
>
> 'm going to sync django.auth.User Table across multiple database. Since, I
> have two databases in my Django project.As we know Django doesn't support
> cross-DB relationship officially. So I'm trying to sync User and Accounts
> table across multiple database.
>
> To create new User object, I have to do something like this:
>
> usrdct = User.objects.get(username='username').__dict__ #from 'default'
> database
>
> What I have to do is that, either
>
> u = User(**usrdct).using('db2')
>
> or
>
> u = User(using ='db2')
> u.__dict__.update(usrdct)
> u.save()
>
> Thanks in Advance
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/vuwJbumfI0sJ.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
> --
> 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 this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
--
*
GlxGuru
*
--
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 this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
``models.BooleanField`` fields default to ``False`` when missing from fixtures
This may be the intended behavior, but I couldn't find docs on it. My recommendation would defer to "The Zen of Python" In the face of ambiguity, refuse the temptation to guess. I would rather see the typical IntegrityError: Problem installing fixture... -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/d2qyWIByy-kJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: The key of permissions model
On 20 September 2012 16:11, Michael Manfre wrote:
> The first argument could be either a string or a list of strings.
Bad pattern. Then you must test for the existence of a string in order
to avoid ('t', 'h', 'i', 's').
HM
--
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 this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
