Hello, I've got a view that serves as a hub so that a multi-page form
has only one url. So when the user goes to the URL it sends them to
the first page of the form, the first page sends back to the hub,
which sends them to the second page and so forth. This worked great
until I required the
Sweet, thank you for all the help guys!
I'll go through all this and figure out which best suits my needs.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Hello,
I've built an app that accepts inputs from the user and then uses them
to do some heavy data crunching. I've got everything working
correctly, however, on some runs the process is too long and the
browser times out before it can complete. Does anyone know a way
around this? Ideally
The problem there was that much of the data I was importing came from
the
site's old MySQL database from before I started using PostGIS and
GeoDjango.
Does anyone know if there's a way to tell Postgresql to automatically
detect what's
in the table and resequence?
On Mar 28, 1:17 pm, "Brian
Yes, of course there is a constraint there: the primary key, which of
course I don't want to remove. Marty's solution was it. Thanks for
the assistance.
On Mar 28, 12:50 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 28, 2008 at 2:35 PM, makebelieve <[E
You, my friend, rule. That's exactly what I needed to do. I've just
recently moved
from MySQL and am at the point in which I appreciate Postgresql's
strictness, but
I am still getting used to it.
On Mar 28, 12:57 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> Given that you say you're working
28, 2008 at 2:10 PM, makebelieve <[EMAIL PROTECTED]> wrote:
> > Saving some of my objects work, but only because early IDs have been
> > removed
> > so it isn't trying to insert an object with an existing ID.
>
> It sounds like you have a unique constrai
the existing data?
Thanks you.
On Mar 27, 7:28 pm, makebelieve <[EMAIL PROTECTED]> wrote:
> I recently made a new production database for a site using the
> following methods:
>
> 1. Ran syncdb to create all tables needed for the project
> 2. Used data transfer in PG Navicat to bri
I recently made a new production database for a site using the
following methods:
1. Ran syncdb to create all tables needed for the project
2. Used data transfer in PG Navicat to bring in old data I need
Now when I try to create a new object in the admin interface I keep
getting:
On Jan 2, 9:48 am, Nathaniel Whiteinge <[EMAIL PROTECTED]> wrote:
> On Dec 30 2007, 6:46 pm, makebelieve <[EMAIL PROTECTED]> wrote:
>
> > Part of a form of mine has a drop down to choose a region which is a
> > foreign key to the object I'm updating. Further,
Part of a form of mine has a drop down to choose a region which is a
foreign key to the object I'm updating. Further, I have a link to add
a new region if the user does not see what they want. If a user adds
a new region it is successfully made in the database, but it will not
show up in the
I figured out a way around it:
def benefits_sql(schema):
from django.db import connection
cursor = connection.cursor()
sql = "select * from %s.benefits" %(schema)
cursor.execute(sql, [])
benefits = cursor.fetchall()
return benefits
I'm writing a custom sql method to grab some data from schemas outside
of public, but the database library is adding quotes to the schema
names which causes an sql error. Any ideas on a way around this?
def benefits_sql(schema):
from django.db import connection
cursor =
I found a way around this. I added a category attribute to the model:
class Message(models.Model):
program = models.ForeignKey(Program)
msgstr = models.TextField(null=True)
def category(self):
return self.program.category
so now:
{% regroup
A simplified version of model is this:
class Category(models.Model):
category = models.CharField(maxlength=100)
class Program(models.Model):
name = models.CharField(maxlength=100)
category = models.ForeignKey(Category)
class Message(models.Model):
program =
Ok, from a previous post I've found that the best way to list items by
a category is to use _set:
{% for c in categories %}
{{ c }}
{% for i in c.item_set.all %}
{{ v }}
{% endfor %}
{% endfor %}
However, what if I want to limit the items based upon one of their
16 matches
Mail list logo
