On 30-Oct-07, at 10:55 PM, webjunkie wrote:
>> Err, what was the old version, and what's the new version?
>>
>> "Upgrade" is kind of vague. :-/
>
> Upgraded from 3.2.10 to 3.3.1 ;)
which is 8 months old ;-)
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
On Tue, 2007-10-30 at 17:03 -0400, George Vilches wrote:
> What I want to do: Assume I have an integer column in a table that
> contains a value that I want perform a bit operation on. I would like
> to able to make a QuerySet that generates a query similar to this:
> "SELECT * FROM table
On Oct 29, 3:31 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> You probably want to start by reading messages here:
>
> http://groups.google.com/group/django-developers/search?q=multi-db...
So it sounds as if the branch is dead, and there are patches being
attached to #4747? I'd be willing to
On Oct 31, 4:25 am, webjunkie <[EMAIL PROTECTED]> wrote:
> On Oct 30, 4:53 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
>
>
> > Err, what was the old version, and what's the new version?
>
> > "Upgrade" is kind of vague. :-/
>
> Upgraded from 3.2.10 to 3.3.1 ;)
Except that I still can't
What I want to do: Assume I have an integer column in a table that
contains a value that I want perform a bit operation on. I would like
to able to make a QuerySet that generates a query similar to this:
"SELECT * FROM table WHERE column & 4;". (example is MySQL-friendly).
I've looked
On Oct 27, 2007 3:12 PM, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
> Is there a reason why setup_environ adds the parent directory of the project
> directory to the path, imports the project module, and then removes the parent
> directory from the path? The imported project module is also not
> On 10/30/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> > James, I think you've managed to hit (what I'd consider) the perfect
> > stride there. You have to import Entry anyway, so by making your
> > constants class attributes, you avoid the extra import requirement.
>
> It's not quite an enum,
On 10/30/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Though on further reflection, I think Jeremy's asking for something
> that's legitimately useful: it'd be nice to have some way to accept
> the human-readable value (say, in a URL) and use it to do the lookup
> with that.
Hrm, I hadn't
On 10/30/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> James, I think you've managed to hit (what I'd consider) the perfect
> stride there. You have to import Entry anyway, so by making your
> constants class attributes, you avoid the extra import requirement.
It's not quite an enum, but it's
James, I think you've managed to hit (what I'd consider) the perfect
stride there. You have to import Entry anyway, so by making your
constants class attributes, you avoid the extra import requirement.
I hereby retract my +0 in favor of a -0. Either way, I'm still stuck at "meh."
-Gul
Wow, that's an interesting idea. I don't think I'd use it very often,
but I definitely like the idea. It would add a little bit of overhead
beyond the existing, but that's only when people actually use it, and
I expect that won't be terribly often.
This seems like the kind of thing that would be
On 10/30/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> It's always bugged me a little that choice lookups are based on the raw value.
>
> Example for discussion:
> CHOICES = (
>(1, 'parrot'),
>(2, 'argument'),
> )
>
> class Profile(models.Model):
> user = FK(User)
> favorite_skit
It's always bugged me a little that choice lookups are based on the raw value.
Example for discussion:
CHOICES = (
(1, 'parrot'),
(2, 'argument'),
)
class Profile(models.Model):
user = FK(User)
favorite_skit = IntegerField(choices=CHOICES)
In staticly-typed languages, and
On Oct 30, 4:53 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
> Err, what was the old version, and what's the new version?
>
> "Upgrade" is kind of vague. :-/
Upgraded from 3.2.10 to 3.3.1 ;)
--~--~-~--~~~---~--~~
You received this message because you are
On 10/30/07, webjunkie <[EMAIL PROTECTED]> wrote:
>
> I had the same problem today. I can confirm that it's fixed with a
> newer mod_python.
> http://groups.google.com/group/django-users/browse_frm/thread/5718bb2a94ebec2
>
Err, what was the old version, and what's the new version?
"Upgrade" is
I had the same problem today. I can confirm that it's fixed with a
newer mod_python.
http://groups.google.com/group/django-users/browse_frm/thread/5718bb2a94ebec2
On Oct 26, 6:59 am, Chris Henderson wrote:
> I ran into this when I was running benchmarks with ab2 on an Ubuntu
> Dapper box. I
The as_* methods are helpers to display the form fields quickly. As
mentioned above you can accomplish exactly what you are describing.
Just create a templatetag to make it more DRY.
On Oct 30, 2:52 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> > On the other hand, it's kind of an edge
--
Warner Leijenaar
---
[EMAIL PROTECTED] [EMAIL PROTECTED]
[w] http://renraw.nl/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
Hello,
I am a new to Django..
i just wanted to know if i could reverse engineer an existing
database tables to Model.py files
is there any tool to do this?
Regards,
Arun
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
> On the other hand, it's kind of an edge case, since if you're using the
> same set of tags for every field, it quite limits the amount of
> customized layout you can do :)
I don't think so - most of the people control the layout via css
I think using {{ form.foo.as_p }} is a great idea.
On 30-Oct-07, at 12:07 PM, aruns wrote:
> I am a new to Django..
dont crosspost to both users and developers - stick to users unless
you are going to join in developing django itself
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
On 29/10/2007, Justin Driscoll <[EMAIL PROTECTED]> wrote:
>
> To me having the two mutually-exclusive arguments sounds too much like
> trying to fake static typing in a dynamic language. I don't see the
> advantage of separate names for basically the same information provided in
> different ways.
22 matches
Mail list logo
