I just sent it to Jacob who said he'd add it to the ticket if I was
still unsuccessful after his suggestion of creating a session :) so it
should be up their shortly.
On Mar 2, 11:38 pm, "Gary Wilson" <[EMAIL PROTECTED]> wrote:
> On Mar 2, 7:38 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
On Mar 2, 10:24 pm, "Simon G." <[EMAIL PROTECTED]> wrote:
> I thought #3579 was more of a generic thing, but well spotted Gary!
Yes, I just changed the title to, what I think, better convey the
intention of poster of the ticket.
--~--~-~--~~~---~--~~
You received
On Mar 2, 7:38 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> If you think this really should work and you can reproduce it, you
> should consider reporting this problem to the Trac team.
Could you attach the file here? I could try my luck and open a ticket
with the Trac project if it fail
I thought #3579 was more of a generic thing, but well spotted Gary!
-Simon
On Mar 3, 5:21 pm, "Gary Wilson" <[EMAIL PROTECTED]> wrote:
> On Mar 2, 6:38 pm, "Simon G." <[EMAIL PROTECTED]> wrote:
>
> > Can you drop by code.djangoproject.com and create a ticket for this,
> > so we don't lose trac (
On Mar 2, 6:38 pm, "Simon G." <[EMAIL PROTECTED]> wrote:
> Can you drop by code.djangoproject.com and create a ticket for this,
> so we don't lose trac (sorry) of it.
Actually, we already have one:
http://code.djangoproject.com/ticket/3579
I have also referenced this thread in the ticket so that
On Mar 2, 2007, at 20:06 , voltron wrote:
> I´m poking around trying to understand things a little more. Can
> someone tell me what the parenthesis in this field declaration is for?
>
> # Code snippet
>
> session_key = models.CharField(_('session key') ...# more code
_() is shortcut for calling
On Mar 3, 2007, at 01:56 , Nebojša Đorđević wrote:
> I'll look into it as fast I can.
I attached a quick fix to the ticket. Try it out.
--
Nebojša Đorđević - nesh, ICQ#43799892
Studio Quattro - Niš - Serbia
http://studioquattro.biz/ | http://code.google.com/p/django-utils/
Registered Linux Use
On Mar 2, 2007, at 09:37 , Brice Carpentier wrote:
> Any idea on how to fix this quickly ?
>
I'll look into it as fast I can.
I opened a new issue (ticket) at http://code.google.com/p/django-
utils/issues/detail?id=12&can=2&q= for this. If anyone find solution
before me please post it there
Hi Todd,
Can you drop by code.djangoproject.com and create a ticket for this,
so we don't lose trac (sorry) of it.
Thanks :)
Simon G.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To p
Please add them to Trac, as it's a good idea to keep an eye on them.
There's a few multi-db bugs/patches out there, e.g.:
http://code.djangoproject.com/ticket/3613
http://code.djangoproject.com/ticket/3301
If one of the trac-admins can add a multi-db value to the "version"
field in Trac, that wo
Hi,
I'm using the multi-db branch to do schema-evolution. I'm bringing
this up to see if it is worth pursuing or if there is some better idea
somewhere...
The basic idea is, have a v1 and a v2 database, with the v1 models in
the first and the v2 models in the latter, and create a v1_to_v2
evolut
I think I've found a bug in the admin's Change Password form. Here's the
call to render the template from the user_change_password function in
django.contrib.admin.views.auth:
return render_to_response('admin/auth/user/change_password.html', {
'title': _('Change password: %s') % esca
I just installed the multi-db branch yesterday and I think it is
something that surely must be supported, and I'll play more with it
the coming time. I have a simple schema-evolution idea that does not
alter existing tables, but simply copies data to new tables in another
database. Don't know if
mmm, I may try this when I get back to work.
Thanks
On 3/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> You can make it save twice by overriding save_file in the filefield
> and call save on new_object before using the pk
>
> On 2 Mar, 19:36, "Brice Carpentier" <[EMAIL PROTECTED]>
> wrote
are you using postgres? if so, when this happens again try typing:
$ ps aux | grep postmaster
do you see more than one process saying something to the effect of
"waiting for transaction?"
you may have created a deadlock (i.e. transaction2 trying to operate
on a locked row, but transaction1 wait
+1 for me too
On 2 mar, 05:33, "olive" <[EMAIL PROTECTED]> wrote:
> +1 for me
>
> On Mar 1, 5:19 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
>
> > On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> > > What about bug #2282? What's the actual status? A patch is proposed,
> > > it doesn't su
I´m poking around trying to understand things a little more. Can
someone tell me what the parenthesis in this field declaration is for?
# Code snippet
session_key = models.CharField(_('session key') ...# more code
Also in the Meta class:
# Code snippet
class Meta:
db_table = 'django_
You can make it save twice by overriding save_file in the filefield
and call save on new_object before using the pk
On 2 Mar, 19:36, "Brice Carpentier" <[EMAIL PROTECTED]>
wrote:
> Like I said, you can't do it pre_save anymore cause revision 4609
> changed the time save_file gets called. The way
Like I said, you can't do it pre_save anymore cause revision 4609
changed the time save_file gets called. The way it works now, when
save_file first get called, your object has not yet been saved, and
thus doesn't have a primary key.
On 3/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> You
You need to do it pre_save
On 2 Mar, 09:37, "Brice Carpentier" <[EMAIL PROTECTED]>
wrote:
> Hi folks.
>
> Since my last svn update, things have been kinda broken in my cms-like
> django application.
> I've been able to track down the issue to the thumbnail app I'm using,
> that does automatic pri
On 3/1/07, Tom <[EMAIL PROTECTED]> wrote:
> Hi it seemed to be a good change to give the admin its own space. Btw
> what about the field specific items like
>
> edit_inline, max_num_in_admin, ...
>
> an so on. Have you made any decision where this should be set in
> future or if this will be left
Trac detected an internal error:
If you think this really should work and you can reproduce it, you
should consider reporting this problem to the Trac team.
Go to http://trac.edgewall.org/ and create a new ticket where you
describe the problem, how to reproduce it. Don't forget to include the
P
On Feb 27, 8:31 pm, "Marc Fargas Esteve" <[EMAIL PROTECTED]> wrote:
> -1 on option 1, and +1 in option 2. We should not remove
> functionality because MySQL can't deal with that, simply document
> "this won't work with mysql" :)
>
+1
Regards!
--~--~-~--~~~---~
Hi folks.
Since my last svn update, things have been kinda broken in my cms-like
django application.
I've been able to track down the issue to the thumbnail app I'm using,
that does automatic primary-key based renaming on ImageFields.
It does that by connecting to the pre_save signal of the model
+1 for me
On Mar 1, 5:19 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote:
>
> > What about bug #2282? What's the actual status? A patch is proposed,
> > it doesn't suit any case but it's a good start for a part of the
> > world.
>
> It still need
25 matches
Mail list logo
