On 7/5/07, RajeshD <[EMAIL PROTECTED]> wrote:
> Not sure. What RDBMS are you using? I understand about the need to
> retain your DB structure as is but are you allowed to *add* new
> constraints to the DB?
Django does not support multi-column primary key tables.
If you'll be doing insert/update/
On Jul 5, 8:44 am, AnaReis <[EMAIL PROTECTED]> wrote:
> Hi again,>From what I could understand, I would have to recreate the database
> so
>
> that django could create an ID field for me. Unfortunately that isn't
> possible because I'm using a legacy database and I can't change it.
Right.
> In
Hi again,
>From what I could understand, I would have to recreate the database so
that django could create an ID field for me. Unfortunately that isn't
possible because I'm using a legacy database and I can't change it. In
this database, the primary key is the two fields combined, so their
combina
Hi again,
>From what I could understand, I would have to recreate the database so
that django could create an ID field for me. Unfortunately that isn't
possible because I'm using a legacy database and I can't change it. In
this database, the primary key is the two fields combined, so their
combina
On Jul 4, 4:35 pm, RajeshD <[EMAIL PROTECTED]> wrote:
> On Jul 4, 12:14 pm, AnaReis <[EMAIL PROTECTED]> wrote:
>
> > Hi again,
> > Thanks for the suggestion, but this still isn't working... the
> > difference between this module and the others that I have already made
> > is that (besides the fa
On Jul 4, 12:14 pm, AnaReis <[EMAIL PROTECTED]> wrote:
> Hi again,
> Thanks for the suggestion, but this still isn't working... the
> difference between this module and the others that I have already made
> is that (besides the fact that the others actually work) this one
> involves a table with
Hi again,
Thanks for the suggestion, but this still isn't working... the
difference between this module and the others that I have already made
is that (besides the fact that the others actually work) this one
involves a table with two primary keys. If it had just one I bet there
would be no probl
Hi Ana,
>
> [views.py]
> level=Level()
> level.level_name=form.clean_data.get('level_Name')
> level.instrument_name=form.clean_data.get('instrument_Name')
> level.available=form.clean_data.get('available')
> level.tablename=form.clean_data.get('tabelname')
>
> level.save()
Hi!
In my project, I'm doing a .save() but nothing is being saved and I
cant figure out why...
The code is:
[models.py]
class LevelForm(forms.Form):
level_Name=RegexField('^level\d[a-b]?$', required=True,
max_length=20, initial='level', error_message='Blah')
instrument_Name=ChoiceField(re
9 matches
Mail list logo
