t_response
1.
response = callback(request, *callback_args,
**callback_kwargs)
...
▶ Local vars <http://meteorite.unm.edu/buildMetCatalog/#>
- /home/wilbur/IOM/iom_catalog/views.py in buildMetCatalog
1.
c1.text(306, 680, header_text,
*
My apache httpd.conf:
Alias /media/ /home/wilbur/IOM/site_media/
Alias /images/ /home/wilbur/IOM/site_media/images/
ServerName meteorite.unm.edu
ServerAlias meteorite.unm.edu
ServerAdmin meteo...@unm.edu
ErrorLog logs/metcat_errors.log
Thanks for responding Shawn,
I am using south, and have tried using a schemamigration --auto on the
database...
I get the error:
? The field 'Photo_Log.sample_id' does not have a default specified,
yet is NOT NULL.
? Since you are removing this field, you MUST specify a default
? value to use f
Hello,
I have changed a number of field names and definitions in my models,
and when I try to add a new record in the Django administration, I get
the following error:
currval of sequence "sample_id_seq" is not yet defined in this session
When I look at the relevant postgresql table, the sequenc
Thanks for your help Daniel, that seems to have fixed my problem...
On May 18, 12:27 pm, Daniel Roseman wrote:
> On Wednesday, May 18, 2011 6:46:49 PM UTC+1, wilbur wrote:
>
> > Hello,
>
> > I continue to get errors when I try to view my model tables in Django
> >
Hello,
I continue to get errors when I try to view my model tables in Django
admin (1.3.0). The errors invariably refer to the name of a foreign
key defined in my models, with the '_id' appended to the name of the
field. My understanding was that by using a 'related_name' in the
column definition
Hello,
I continue to get errors when I try to view my model tables in Django
admin (1.3.0). The errors invariably refer to the name of a foreign
key defined in my models, with the '_id' appended to the name of the
field. My understanding was that by using a 'related_name' in the
column definition
When loading a Django page, I get the error:
IntegrityError while rendering: duplicate key value violates unique
constraint "menus_cachekey_pkey"
I am using Django 1.2.4
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, se
I definitely need to keep the database, and have South installed, but
should I get rid of the original primary key and the sequence it
depends on? Will south add in the new ID field?
On May 10, 11:48 am, Shawn Milochik wrote:
> If you don't mind losing all your data you can destroy the database t
I will try just removing it from the model. Does this mean I should
remove the sample_id variable from the Postgres database as well. Will
running syncdb create the new id field for that table?
On May 10, 10:33 am, wilbur wrote:
> Using exclude works to eliminate this sample_id field from
Thanks for helping on this Shawn...
My model definition looks like this:
class Sample(models.Model):
met_type = models.ForeignKey(MetType, verbose_name='Meteorite
Type')
sample_name = models.CharField(max_length=100,
verbose_name='Sample Name')
sample_id = models.IntegerField(primary
Using exclude works to eliminate this sample_id field from the form,
but I get a
'Null value in column "sample_id" violates not-null constraint'
If one inserts a record directly through Postgresql command line, the
sample_id field gets incremented automatically with its sequence, but
it does not
I am using Django 1.2.4 with a Postgresql 8.4 backend. Before creating
my models in Django, I began with a existing Postgresql database with
tables for which I had defined integer primary keys that used an
autoincrementing sequence on table inserts. When I created my Django
models, I defined the pr
With my current setup, the autoincrement variable set in postgresql is
visible in the Django admin as "Sample_ID", with an empty form field.
The user can't possibly know what the next value in the sequence
should be, so I'm wondering how to deal with the field, as it is Not
NULL, and any attempt to
I am using Django 1.2.4 with a Postgresql 8.4 backend. Before creating
my models in Django, I began with a existing Postgresql database with
tables for which I had defined integer primary keys that used an
autoincrementing sequence on table inserts. When I created my Django
models, I defined the pr
Hello,
I am using Django version 1.2.4 on Ubuntu 10.04. When I try to click
on an individual database table record in the Django Administration
interface (for editing, for example), I get the following error:
TemplateSyntaxError at /admin/iom_catalog/sample/610/
Caught TypeError while rendering:
is middleware from the python interpeter?
> If not check your python path.
>
>
>
> On Thu, Dec 9, 2010 at 11:25 PM, wilbur wrote:
> > Hello and thank you,
>
> > Removing south worked fine. I initially had problems loading
> > middleware classes to setting
, but will allow you to use django cms.
> If you later fix the south, just run
> ./manage.py migrate cms --fake
>
> to fake all cms migrations currently in the project.
>
>
>
> On Thu, Dec 9, 2010 at 7:13 PM, wilbur wrote:
> > Hello,
>
> > I am having a hell o
Hello,
I am having a hell of a time getting Django-CMS up and running. I am
using Django 1.1.1, and South 0.7.3 (by way of using easy_install
south systemwide, though my Ubuntu synaptic package manager says
0.6-1) on Ubuntu 10.04 (Lucid). I am following the CMS tutorial at
http://readthedocs.org/p
19 matches
Mail list logo
