Przemek Gawronski wrote:
>
> What I'm looking for now is, how to redirect to a different page with
> the button, and sending to the page (django view) the id number.
>
> Przemek
If you don't want to use ajax you can either use a form as normal to
submit it and then issue a redirect at the serv
I seem to be having a bit of a problem with the depth parameter to
select_related.
If I have only simple relationships, i.e. only three tables involved
linked by a simple foreign key chain it all *seems* to work OK. I get
the right data in both model instances with just the one query issued to
Przemek Gawronski wrote:
> I want to show to the user a list of workorders with the possibility
> to select one (probably I should use a radio button for that), above
> the list are a couple of buttons that allow to display some extra
> information for the selected workorder like a list of time sh
I can't say I've used Tortoise SVN through a proxy before and I've never
seen that error. You might be better off asking the guys over at
Tortoise SVN what that error means.
Regards,
Gary.
tsc wrote:
> Sorry, but I've forgotten to set the proxy server in Tortoise. Now it
> worked a little bett
I use Tortoise SVN for windows XP without any problems. I update from
trunk almost daily.
It's certainly the right url that you have. What version of Tortoise SVN
are you using? Can you browse the repository?
The other way to get it would be to use the Subversion command line
tools themselves
Mike H wrote:
> Hi all,
>
> Is there a recommended solution for connection pooling with postgres?
> I've seen SqlRelay and pgpool mentioned but they both seem to have
> downsides in terms of affecting query performance. What have people here
> used?
>
I use pgpool and it works brilliantly.
Yeah, I'd actually considered that. We do use that method on another
product.
The big upside is that you don't have to store exceptions if you remove
just one date in the future from the recurrence pattern, you just remove
that one date record from the database.
There can be a big downside de
>
> So in your Event model (or whatever you're calling it), you're
> essentially storing the keyword arguments to an rrule, depending on
> what's necessary for a particular event?
>
> Then whenever you need to render a calendar, you pull in all the
> Events from the db, create rrules for each usin
I'm working on this very problem.
The best way I have found so far is to use the rrule stuff from the
python-dateutil package.
Given a repeat interval such as DAILY, WEEKLY, MONTHLY etc. it can
generate all the dates that your event occurs on between two dates.
It will even generate for just
On Monday 16 October 2006 18:01, Mike wrote:
> The server is rather new. 2GB of memory with a top grade Opteron (not
> sure which). Once again, the server is running with low load for most
> of the day, and as much as I want to, I have hard time believing its
> the server that is to blame.
But it
On Wednesday 13 September 2006 14:41, James Bennett wrote:
> I've written about that in a "quick summary" sort of way; you might
> want to read it:
> http://www.b-list.org/weblog/2006/06/04/lets-talk-about-frameworks-dba-edit
>ion
Thanks James, a nice "generic" summary.
For my part I would summa
>
> This comes up every once in a while, and every once in a while I post a
> link to my solution to this issue from a while back:
>
> http://code.djangoproject.com/ticket/1007
>
> This patch, while it might need some small tweaks to work against
> recent trunks, lets you essentially turn this
On Tuesday 12 September 2006 23:02, James Bennett wrote:
> On 9/12/06, Gary Doades <[EMAIL PROTECTED]> wrote:
> > You mean every TYPE of object surely. I'd like to see it list 10 million
> > records :)
>
> Nope. It lists the objects.
Ok, I'll be sure to
On Tuesday 12 September 2006 21:30, James Bennett wrote:
> There are some checks in place for this; the admin app, for example,
> will display a confirmation page before allowing a delete, and that
> page lists every related object that will be deleted.
You mean every TYPE of object surely. I'd l
On Tuesday 12 September 2006 10:01, Gábor Farkas wrote:
> hi,
>
> as far as i understand,
>
> when you delete an object in django, it also deletes all the objects
> that reference it.
>
> is there a way to only delete the object, and get an exception if other
> objects reference it?
>
Oh dear, I
15 matches
Mail list logo