Hello and Hi
Today, I tell you another Best
Website for finding the best job.
Please check this link and enjoy
your dream job.
http://www.it-jse.com
Special thing about this website
is, they are presenting direct links to jobs.
They are using only Direct
Employers and not using Staffin
I created a ticket for this http://code.djangoproject.com/ticket/2025
--~--~-~--~~~---~--~~
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.co
I created a ticket for this: http://code.djangoproject.com/ticket/2025
--~--~-~--~~~---~--~~
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.
I've posted an intial revised version of my summer of code proposal at:
http://code.djangoproject.com/wiki/GenericAuthorization
This should go hand in hand with Chris Long's RowLevelPermissions project:
http://code.djangoproject.com/wiki/RowLevelPermissions
Also, for the curious, you c
After reviewing the relevant source code base a little, I have started
with the implementation of the schema evolution skeleton (which will
contain a functional "Add Field" support).
http://case.lazaridis.com/multi/wiki/DjangoSchemaEvolution
With a very small assistance from the team (mostly s
On 5/28/06, gabor <[EMAIL PROTECTED]> wrote:
> further debugging showed, that psycopg is at fault, because it quotes
> byte-string params, but not unicode-string params.
>
> also, take an unicode string, like u"gábor" (my name :-). you can assign
> it into a charfield, and if you save the model usi
Hi Chris,
The implementation detailed on the wiki appears to give the granularity
that several people around here (including myself) have been looking
for, minus the various points that have already been brought up. An
ACL-type solution as opposed to UNIX-style permissions certainly seems
more fl
I got curious about how Django deals with deletes in cases where an
object refers to some other object as I noticed that this seemed to
happen automagically in the admin interface. So I set up a silly little
example:
class Company(models.Model):
name = models.CharField(maxlength=50)
def
hi,
i was wondering if it would be better to simply reject unicode data in
django models. at least until better unicode support
(http://code.djangoproject.com/wiki/UnicodeInDjango) arrives...
that would mean that django would raise an exception when you try to
assign unicode text into a text-
