On 9/16/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 9/15/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > In general, initial SQL data is a real pain to manage and if anybody has
> > a good idea on a better approach. I would like to avoid building a full
> > SQL parser in Python for o
Has anyone managed to get it working as of the latest release?
http://code.djangoproject.com/wiki/FullHistory
Tried doing it on a fresh db and all and nothing.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
On Fri, 2006-09-15 at 20:32 -0700, [EMAIL PROTECTED] wrote:
> Hi Malcolm & James,
>
> I do think the SQL initial data is going to be a problem in a number of
> ways:
>
> 1) database API's (as per this thread)
>
> 2) line breaks ( c.f. http://code.djangoproject.com/ticket/2729 )
>
> 3) database
On 9/16/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> And anybody who wants to introduce a method called _init() in addition
> to Python's existing __init__() is clearly a wanna-be Perl programmer
> and should be viewed with caution in any case. :-)
:-)
Truth be told, I'm not particularly
Hi Malcolm & James,
I do think the SQL initial data is going to be a problem in a number of
ways:
1) database API's (as per this thread)
2) line breaks ( c.f. http://code.djangoproject.com/ticket/2729 )
3) database specific issues. For example - the sql file attached to the
ticket above (2729)
On Sep 16, 2006, at 10:16 AM, Malcolm Tredinnick wrote:
> [I'm a leading advocate for the "give Gabor a unicode branch in svn"
> school, btw, so that you and he and others can go nuts and just do
> it.]
+1 on the "give Gabor a unicode branch in svn" school. It's really
important to non-Engl
I have to admit that reading such informative issue reporting and
django experience sharing email is always a pleasure.
It's also interested to know that your path from PHP -> Rails ->
Pylons -> Django. Maybe in another email thread, would like to know
the reason behind your going beyond Pyl
On Fri, Sep 15, 2006 at 09:25:37PM -0500, James Bennett wrote:
>
> On 9/15/06, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
> > Inter-field dependency. For example:
>
> Most of this looks like it can be much more flexibly handled by the
> already-available validator syntax (which, I assume, wi
On Fri, 2006-09-15 at 21:22 -0500, James Bennett wrote:
> On 9/15/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > In general, initial SQL data is a real pain to manage and if anybody has
> > a good idea on a better approach. I would like to avoid building a full
> > SQL parser in Python for
Hey Gabor,
On Thu, 2006-08-31 at 09:16 +0200, Gábor Farkas wrote:
[...]
> let's say you have a model called Owner, that references using a
> foreignkey a Thing.
>
> =
> class Thing(Model):
> name = CharField(maxlength=500)
> =
>
>
> ==
On 9/15/06, Scott Paul Robertson <[EMAIL PROTECTED]> wrote:
> Inter-field dependency. For example:
Most of this looks like it can be much more flexibly handled by the
already-available validator syntax (which, I assume, will be finishing
its migration into the model system).
--
"May the forces
Hey Russell,
On Mon, 2006-09-11 at 20:34 +0800, Russell Keith-Magee wrote:
> On 7/8/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > To all Django committers --
> >
> > Please don't change any code within django.db.models over the next few
> > days. Stimulated by ticket #2306, I took a look
On 9/15/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> In general, initial SQL data is a real pain to manage and if anybody has
> a good idea on a better approach. I would like to avoid building a full
> SQL parser in Python for obvious reasons.
Other people already *have* built SQL parsers
Hi Ivan,
On Sat, 2006-09-16 at 00:20 +0400, Ivan Sagalaev wrote:
> A bit of discussion in Track has reminded me of one thing that I wanted
> to write long ago. So I decided not to spam any tickets and write it here.
>
> There are tickets that appear from time to time that deal with
> unicode-r
Hey Gary,
On Thu, 2006-09-14 at 02:09 +, Gary Wilson wrote:
[...]
> Ok, after some trial and error, I see that if you have null=True on a
> CharField, it will use NULL instead of empty string. This is what I
> needed because in my model I have a field that I want to be optional
> but unique.
Turns out when I was trying to apply ticket 2070, I was forgetting to
actually enable the upload middleware.
I've enabled it now, but I'm getting errors. This patch *should* fix
the problem if I can get it working.
--~--~-~--~~~---~--~~
You received this message
On Mon, 2006-09-11 at 02:07 +, Martin wrote:
> Hi,
>
> I was wondering if there is a particular reason why the current value
> of a `named` cycle is not exported into the context so that it is
> accessable later in the tamplate as variable as well?
>
> Fore example:
>
> {% for obj in object
Hi Simon,
On Thu, 2006-08-31 at 00:54 -0700, [EMAIL PROTECTED] wrote:
> Hello Djangonauts,
>
> I've found an issue with initial data and SQLite - if any of the fields
> in the initial data has a "%" in it, the import fails. Pysqlite is
> apparently processing the query for string formatting args
On Wed, 2006-08-30 at 22:58 +0200, [EMAIL PROTECTED] wrote:
> Hi James,
>
> James Bennett schrieb:
> > On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> The committer russelm said: Template variable evalution should follow
> >> Python norms.
> >
> > As I understand it, the distinctio
On Tue, Sep 12, 2006 at 02:35:54PM -0500, Adrian Holovaty wrote:
> Let's change this to be similar to model classes, like so:
>
> class ContactForm(Form):
> sendername = TextField()
> senderemail = EmailField()
> subject = TextField(maxlength=20, blank=True)
> message = TextField()
The error seems to be related to this code in db/models/query.py:
for related in cls._meta.get_all_related_many_to_many_objects():
for offset in range(0, len(pk_list), GET_ITERATOR_CHUNK_SIZE):
cursor.execute("DELETE FROM %s WHERE %s IN (%s)" % \
Oh, and interestingly, the row level permission I was trying to delete
*does* in fact get deleted, despite my seeing this error.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To p
I'm going to keep lobbing them at you, until it all works :)
I'm still trying to delete a row level permission, and I'm getting:
Traceback (most recent call last):
File
"/Users/jayparlar/Library/Python2.4/site-packages/django/core/handlers/base.py"
in get_response
74. response = callback(requ
Deryck Hodge wrote:
> Don't take my comment on the one ticket (#2727) as dev's rejecting the
> patch.
I don't :-). It really just has reminded me of this thing I wanted to
write long ago but forgot...
--~--~-~--~~~---~--~~
You received this message because you ar
Hi, Ivan.
On 9/15/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
>
> A bit of discussion in Track has reminded me of one thing that I wanted
> to write long ago. So I decided not to spam any tickets and write it here.
>
> There are tickets that appear from time to time that deal with
> unicode-rela
A bit of discussion in Track has reminded me of one thing that I wanted
to write long ago. So I decided not to spam any tickets and write it here.
There are tickets that appear from time to time that deal with
unicode-related issues in various places. The problem is that patches
are rejected w
Hi, all.
Haven't seen any activity in a couple days on django-updates. Is
something wrong with the list?
Cheers,
deryck
--
Deryck Hodge http://www.devurandom.org/
Web Developer, Naples News http://www.naplesnews.com/
Samba Team
Fixed in the latest revision.
Thanks,
Chris
--~--~-~--~~~---~--~~
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 unsubscribe from th
28 matches
Mail list logo
