Here's what I've found...
Start with the very useful tutorial at
http://www.djangoproject.com/documentation/forms/ - in general it's
very helpful, but there are some small gaps in the documentation, which
would certainly have helped me
#1: I'd emphasize that this document
(http://www.djangoproje
i had to took of the leading ^ to make it works
127.0.0.1/cefinban/admin would not match any url if ^admin.
SetHandler python-program
PythonHandler django.core.handlers.modpython
PythonPath sys.path+['/home/greg/Projects']
SetEnv DJANGO_SE
On 1/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Sorry if these are just rehash questions, I wasn't able to find the
> ansewers on the DJ site. Proabably user error :)
A full list of the changes being made in the magic-removal branch is
online here:
http://code.djangoproject.com/wiki/
All,
After the magic removal, will it be possible to:
a.) connect to multiple databases: ex. Legacy database A and new
database B for a single application ?
b.) Be more specific when defining data types in the model: ex.
using big-serial rather than serial for the primary key?
Sorry if
hi, i am writting a generic create object view for my recipe model.
i can get the form display well using this kind of code :
Nom de la recette {{form.nom}}
ect ..,
But is there a way of automatically checking if {{ form.nom }} is a
recquired field ? (and therefore put a star near it like this).
On Tuesday 31 January 2006 21:38, Adrian Holovaty wrote:
> Nice explanation, Luke! I've added it to the FAQ.
I noticed it in django-updates, and thought "that sounds really
familiar"!
Luke
--
"Ineptitude: If you can't learn to do something well, learn to enjoy
doing it poorly." (despair.com
On 1/31/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> The Django ORM basically assumes a third normal form database design.
> It half enforces this by adding a primary key to every table (if you
> don't specify one yourself), and only allows one field to be a primary
> key in the class definition.
On Tuesday 31 January 2006 14:46, Rudolph wrote:
> Hi,
>
> I couldn't get the magic removal branch started without spending time
> on fixing some errors (createsuperuser didn't work and runserver told
> me "No module named sessions"). Could someone with a bit more Django
> experience than me, try
On Tuesday 31 January 2006 16:59, kggroups wrote:
> I'm considering building my next web app in either Django or Rails
> because I'm sick of php. Before I jump in though, I was wondering
> how django handles multicolumn keys.
If you need to, you can specify constraints using unique_together - se
On 1/31/06, Andu <[EMAIL PROTECTED]> wrote:
> Trying /django/, /django/admin/, /django/djtest/ or
> /django/djtest/admin/ I get the same error as previously mention.
>
> Any ideas what I'm doing wrong?
Have you tried just '/admin/'? That's what the default "un-comment
this line for admin" bit in
Hi everyone,
I'm having problems with making Django work ok. I have a debian box
with mod_python 3 and Django installed ok. I started to follow the
tutorial and got to the admin area part. This is where I can't make it
work.
Django's webserver works fine.
Apache2 and mod_python yeld the error:
Don't know if this is applicable to you situation, but what I've done
when I want to use the manipulator to validate a subset of fields is
the following:
1. pass your copy of the POSTed data containing the subset of data you
want to validate to the manipulator as normal for validation. The
errors
Aany "model" can be included in the admin interface as long as you
include a META subclass inside of it with the admin attribute defined:
class Tagged(meta.Model):
user = meta.ForeignKey(User)
site = meta.ForeignKey(Site)
tag = meta.ForeignKey(Tag)
class META:
admin=meta.Adm
wow. that is pretty simple. thanks for the response.
i'm guessing adding additional attributes to the Tagged class would not
be a problem? for example, a date, etc?
Would even the Tagged class have an admin form prebuild?
Hi Jason,
On Tuesday 31 January 2006 09:36, [EMAIL PROTECTED] wrote:
> hi,
>
> I want to do something like this:
[...]
> class Foo(Taggable, Noteable):
> name = meta.CharField(maxlength=255)
>
> def __repr__(self):
> return self.name
>
> class META:
> admin = meta.Admi
hi,
I want to do something like this:
from django.core import meta
class Tag(meta.Model):
text = meta.CharField(maxlength=255)
def __repr__(self):
return self.text
class META:
admin = meta.Admin()
class Taggable(meta.Model):
tags = meta.ManyToManyField(Tag, b
Something like this for your models:
class User(meta.Model):
name = meta.CharField()
class Website(meta.Model):
url = meta.CharField()
class Tag(meta.Model):
name = meta.CharField()
class Tagged(meta.Model):
user = meta.ForeignKey(User)
site = meta.ForeignKey(Site)
ta
I'm considering building my next web app in either Django or Rails
because I'm sick of php. Before I jump in though, I was wondering how
django handles multicolumn keys. It seems like django is geared more
toward keeping separate tables for different types of things and using
single column joins
On 1/31/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
> On 1/31/06, aaloy <[EMAIL PROTECTED]> wrote:
> >
> > 2006/1/31, Kenneth Kalmer <[EMAIL PROTECTED]>:
> > >
> > > One thing however, the system will need a fair amount of CLI apps that
> > > will interact with other systems doing things like autom
Hi,
I couldn't get the magic removal branch started without spending time
on fixing some errors (createsuperuser didn't work and runserver told
me "No module named sessions"). Could someone with a bit more Django
experience than me, try the code on the magic removal branch? Or does
someone know a
On 1/31/06, aaloy <[EMAIL PROTECTED]> wrote:
>
> 2006/1/31, Kenneth Kalmer <[EMAIL PROTECTED]>:
> >
> > One thing however, the system will need a fair amount of CLI apps that
> > will interact with other systems doing things like automated
> > webservice calls and file transfer to name two. The sy
2006/1/31, Kenneth Kalmer <[EMAIL PROTECTED]>:
>
> Guys
>
> I've been doing some extensive reading on frameworks recently, and
> dango definitely looks like the solution to a huge project that I'm
> undertaking at the moment. It provides several features that key
> including multiple applications
I don't know the Django API very well, however it might make sense to
support the date extraction functions offered by various
databases. I have to admit that I only use Oracle and Sql Server
at work, however I know that they support month, day, year, day of
week, day of year, week number datepart
On 1/31/06, Jamison Roberts <[EMAIL PROTECTED]> wrote:
> I don't know the Django API very well, however it might make sense to
> support the date extraction functions offered by various databases.
-1.
As an app developer, I don't want to think about which DB supports
which date parts. I already
Guys
I've been doing some extensive reading on frameworks recently, and
dango definitely looks like the solution to a huge project that I'm
undertaking at the moment. It provides several features that key
including multiple applications on a single database.
One thing however, the system will ne
On Tue, 31 Jan 2006 02:00:53 +0200, Oliver Rutherfurd
<[EMAIL PROTECTED]> wrote:
Hi Amit,
On 1/30/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
On 1/31/06, Oliver Rutherfurd <[EMAIL PROTECTED]> wrote:
> The use case for this is a long registration process, where different
> data points fro
Thanks for your help.
I changed my code to the version below but it didn't solve the problem.
I'll try the magic-removal-branch and post my result here.
Rudolph
from django.core import meta
class Language(meta.Model):
abbreviation = meta.CharField('Two-letter abbreviation',
maxlength=2, un
On 1/31/06, Oliver Rutherfurd <[EMAIL PROTECTED]> wrote:
Hi Amit,> I would recommend creating your own FormManipulators, one for each page.> Validate page level manipulator and save the content in request.session, and> when you are done on the last page, pick out all the saved temproary states
> an
28 matches
Mail list logo
