Duc Nguyen wrote:
> On a somewhat related note, is it just me or does no django core developer
> follow the "no line longer than 79 characters" note. I like using emacs
> and I have my frame width set at 80 and it bothers me to no end to have
> to scroll to see every line. Turning on line wrappi
I favor Adrian's style.
On a somewhat related note, is it just me or does no django core developer
follow the "no line longer than 79 characters" note. I like using emacs
and I have my frame width set at 80 and it bothers me to no end to have
to scroll to see every line. Turning on line wrappin
On 26-Jul-07, at 7:36 AM, Thejaswi Puthraya wrote:
> This week I worked on getting the 'like' and 'between' check
> conditions into the project and also writing a lot of doctests.
could you post this to the users list also - you may get a lot of
feedback from the user's point of view
--
re
Hello Django Developers,
This week I worked on getting the 'like' and 'between' check
conditions into the project and also writing a lot of doctests.
So here is how to use 'like' and 'between' check constraints
class Manufacturer(models.Model):
mfg_name= models.CharFiel
Adrian recently corrected some of my docstring additions [1][2], and I
am posting this to the list so that we can get an official stance on the
matter. I also suggest we add the decision to the "Coding style"
section of the "Contributing" documentation for consistency of future
patches, since
> That's not a great answer, but in the meantime, you might want to take
> a look at the lazy instantiation in the GIS branch[1]. That code isn't
> exactly what you want, but it might help get you started on a
> descriptor-based approach to do what you're asking for until there's a
> proper soluti
On 7/25/07, z0n3z00t <[EMAIL PROTECTED]> wrote:
> Does anyone have any idea how I could hook into and change the field's
> value as soon as the value gets loaded from the db?
This is something that's been raised before, and there were a few
ideas proposed. Malcolm's looking over a variety of Fiel
I'm trying to create a custom CharField that would encrypt a field's
contents before saving to the db, and conversely decrypt the field's
values from the db as it loads (using a public key).
I want to make sure that the contents of this field is encrypted in
the database, but decrypted whenever I
I just came up with a setup that works perfectly for me as it allows
me to work on project specific apps as well as on portable apps
efficiently.
The setup is here:
http://groups.google.com/group/django-users/browse_thread/thread/ab9e4730b092b81d/419ddcc572954ff8#419ddcc572954ff8
I want to add
