On Wed, 2009-03-04 at 08:20 -0800, boyombo wrote:
> I encountered the issue written about in Ticket #4140 while deploying
> an application on oracle. I later found that the problem stemmed from
> me using field name 'date', which is a keyword, in some of my models.
> I did my development on MySQL.
On Wed, 2009-03-04 at 18:36 -0200, Ramiro Morales wrote:
> Hi all,
>
> I'm working on fixing and updating the patch for this ticket and found that
> neither cx_Oracle nor pysqlite2/sqlite3 connection cursor() methods take *args
> and **kwargs parameters.
>
> Further research shows that the same
On Wed, 2009-03-04 at 09:28 -0800, Tim Graham wrote:
> Hi,
>
> http://docs.djangoproject.com/en/dev/misc/distributions/ is rather out-
> of-date with respective to the versions of Django that are shipping
> with each OS. A summary of tickets that are currently accepted:
>
> 8417 - request to ad
Hi all,
I'm working on fixing and updating the patch for this ticket and found that
neither cx_Oracle nor pysqlite2/sqlite3 connection cursor() methods take *args
and **kwargs parameters.
Further research shows that the same is true for mysql-python.
The current patch for this ticket adds these
When trying to add an object of the wrong type using a related
manager, Django fails silently rather than complaining as specified in
the docs:
http://docs.djangoproject.com/en/dev/topics/db/queries/#saving-foreignkey-and-manytomanyfield-fields
I've created ticket #10413 and added a patch to add
Hi,
http://docs.djangoproject.com/en/dev/misc/distributions/ is rather out-
of-date with respective to the versions of Django that are shipping
with each OS. A summary of tickets that are currently accepted:
8417 - request to add ArchLinux
8497 - request to add OpenSolaris
9606 - request to add
On Mar 4, 2009, at 8:29 AM, PauloS wrote:
>
> On Mar 3, 1:55 pm, Alex Gaynor wrote:
>> Looking at the patch IMO it should still dot he
>> filter(**{self.fk.name:
>> self.instance.pk}) even if you provide a queryset.
>
> You are right again. Would you mind to look again and give any advice
>
I encountered the issue written about in Ticket #4140 while deploying
an application on oracle. I later found that the problem stemmed from
me using field name 'date', which is a keyword, in some of my models.
I did my development on MySQL.
I think this problem should be documented properly, perha
thanks guys - ya this is indeed the wrong forum - i was just looking
for some info / ideas - thanks a lot for the input
On Mar 3, 6:17 pm, Russell Keith-Magee wrote:
> On Tue, Mar 3, 2009 at 10:51 PM, timmyt wrote:
>
> > my buddy and i have created a Standard CRUD (SCRUD) spec that we'd
> > lik
On Mar 3, 1:55 pm, Alex Gaynor wrote:
> Looking at the patch IMO it should still dot he filter(**{self.fk.name:
> self.instance.pk}) even if you provide a queryset.
You are right again. Would you mind to look again and give any advice
(I'm as crude in python as in English).
Thanks!
--~--~--
Hi Russ and all,
On Wednesday 04 March 2009, Russell Keith-Magee wrote:
>
> 1) Now isn't the time in the Django development cycle for new
> proposals. [...] If you wait a bit, you'll find you get more
> attention for your proposals.
>
Point taken.
> 2) [...] Your proposal spends a lot of tim
On Mon, Mar 2, 2009 at 11:55 PM, Shai Berger wrote:
>
> Hi Django developers,
>
> This is my first message here. I wish to resurrect Application (default)
> settings modules -- a topic that has been discussed here several times. I
> bring it up because I believe its current resolution is inadequa
12 matches
Mail list logo
