I've done a lot of applications with this kind of concern. But it really
doesn't change the design much. The web server goes on one side of the DMZ
and the database server goes on the other. That probably should be the
standard anyway, keep as little extraneous data as possible on the web
server.
I've had a very similar problem and it turned out to be a permission
problem. I had used svn to get the latest django in my home directory and
then linked django from there to /usr/lib/python2.4/site-packages. The
apache user had read/execute privileges up the /usr/lib pathway to
django/core/hand
Why not just use AJAX, and then have a save button to submit and save in
your database.
On Mon, Jul 7, 2008 at 2:48 PM, Bear <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I'm new with Django and I can't figure out a method to do what I want,
> that is to say inserting html dynamically in my page (I'm not
I don't think there is a "right(tm)" way, but there are some things to
consider. A lot of people would argue that a unique characteristic makes a
very good primary key, I think I might be one of them. But, remember that
data reflects the real world. In general, a person's name isn't very
unique.
You can pass it in the URL, mywebsite.com/14/add. You can pass it field.
Assuming you have another page for selecting bar, you can pre-populate a bar
field in the add foo page. That way the user knows what bar he selected
earlier. Then it comes back with the form. You can use a select control
w
5 matches
Mail list logo