Thanks, posted: http://code.djangoproject.com/ticket/1528
--~--~-~--~~~---~--~~
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 unsubsc
On 3/21/06, Matt Good <[EMAIL PROTECTED]> wrote:
> Jeremy, thanks for uploading my patch. I though you'd be interested to
> know that I recently contacted the pymssql authors and they've agreed to
> relicense it under the LGPL instead of the GPL, so it should be usable
> in Django. Keep an eye o
On Mar 21, 2006, at 3:43 PM, Ian Holsman wrote:
> you might also want to split reads/writes up as well.
>
> one thing i investigated was doing this in the DB layer with a tool
> called sequoia http://carob.continuent.org/LibMySequoia
> It emulates a mysql client, but you can sequoia how to divide
limit_choices_to is broken in m-r, it seems. The attached patch fixes
it I think, but as I don't know as much about this as I'd like and it's
1.00am here, I'm not going to commit it.
It seems that limit_choices_to is currently an attribute on the Options
class (aka Meta and ._meta). It's als
On 3/21/06, ak <[EMAIL PROTECTED]> wrote:
>
> I wrote a small path to fix this problem. Does anyone need it ? Where
> should I post it ?
Hi Anton,
If you have found a bug, log a ticket at
http://code.djangoproject.com/newticket, and mark the issue as a
defect.
Before you log your bug, have a qu
Hey there,
Example application. I have a table/set of appliance stores, selling
refrigerators, ovens, dryers.. the whole lot. So:
class Store:
name = meta.CharField
class Appliance:
type = meta.CharField
class InventoryItem:
store = meta.ForeignKey(Store)
appliance = meta.ForeignKey(
Hi all,
I've got an app that has a long form which requires a fair amount of
descriptive text, usually at the beginning of a section of form fields.
Apart from this, it is a perfect fit to the admin functionality.
What do people think about the attached patch? It adds an optional
'descript
I think support should be added for accessing multiple databases in one
application/project. In the current organization where I work, I may have
two databases to work with, one Oracle and one MySQL. I think this would
be pretty easy to setup, it would just need to look like this:
class ObjectF
On 3/22/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On Mar 21, 2006, at 3:13 PM, Alan Bailey wrote:
> > I think support should be added for accessing multiple databases in
> > one application/project.
>
> Me too!
you might also want to split reads/writes up as well.
one thing i investiga
On Mar 21, 2006, at 3:04 PM, Alan Bailey wrote:
> foo = stores.get_list(appliance_list__contains='Whirlpool Fridge
> XC-350')
Right now on the trunk this isn't possible.
However, on the magic-removal branch -- which will become Django 1.0
-- you can indeed query foreign key relations from "b
On Mar 21, 2006, at 3:13 PM, Alan Bailey wrote:
> I think support should be added for accessing multiple databases in
> one application/project.
Me too!
> I think this would be pretty easy to setup, it would just need to
> look like this:
Awesome -- should I expect a patch today, or tomorro
Is there a reason why get_count() (or count() in m-r) doesn't respect
the distinct=True argument? I played around with it some, and got it
working with distinct, but I'm hardly an SQL expert, and I only have
MySQL available for testing. Should I submit a ticket/patch on this, or
am I missing a rea
On 3/21/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> Has something like the following syntax been discussed here before?
>
>Article.objects.filter(Article.author.name == 'fred')
>Article.objects.filter(Article.author.name.contains('fred'))
>etc
Yeah, that's been discussed and sho
Am 19.03.2006 um 08:12 schrieb Max Battcher:
> Russell Keith-Magee wrote:
>> You still need to parse kwargs to handle queries across joins (e.g.,
>> Article.objects.filter(author__name__exact='fred'))
>
> Just playing around with ideas, but what if you could do something
> like:
>
> Article.obje
Hello guys
After playing with Django 0.91 I've found that it behaves not 100%
correct when MySQL 4.1 is used.
File django/core/db/backends/mysql.py contains code:
if self.connection.get_server_info() >= '4.1':
cursor.execute("SET NAMES utf8")
It means that unicode will be al
15 matches
Mail list logo
