On 5/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'm not sure why "year is out of range" is a problem - maybe because
> the table has TIMESTAMP column types? Here is the SHOW CREATE TABLE
> for the registrant table:
>
> CREATE TABLE `registrant` (
> `seminar_id` int(11) NOT NULL default '0',
> `continue_id` varchar(255) NOT NULL default '',
> `customer_id` int(11) NOT NULL default '0',
> `registrant_num` smallint(6) NOT NULL default '0',
> `registration_option` varchar(255) NOT NULL default '',
> `payment_option` varchar(255) default NULL,
> `card_type` varchar(255) NOT NULL default '',
> `transaction_id` varchar(255) NOT NULL default '0',
> `invoice_num` varchar(255) NOT NULL default '0',
> `confirmation_sent` smallint(6) default NULL,
> `payment_received` smallint(6) default NULL,
> `name` varchar(255) NOT NULL default '',
> `email` varchar(255) NOT NULL default '',
> `address1` varchar(255) NOT NULL default '',
> `address2` varchar(255) NOT NULL default '',
> `city` varchar(255) NOT NULL default '',
> `state` varchar(255) NOT NULL default '',
> `zip` varchar(255) NOT NULL default '',
> `phone` varchar(255) NOT NULL default '',
> `name_tag` varchar(255) NOT NULL default '',
> `special_needs` text NOT NULL,
> `seminar_days` varchar(255) NOT NULL default '',
> `last_modified` timestamp NOT NULL default CURRENT_TIMESTAMP on
> update CURRENT_TIMESTAMP,
> PRIMARY KEY (`continue_id`,`registrant_num`),
> KEY `seminar_id_ind` (`seminar_id`),
> CONSTRAINT `registrant_ibfk_1` FOREIGN KEY (`seminar_id`) REFERENCES
> `seminar` (`seminar_id`) ON DELETE CASCADE ON UPDATE CASCADE
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1
>
> This is running Django pulled from svn this morning, python 2.4.2,
> MySQL 4.1.19 and MySQLDB-python 1.2.1-p2
Hi Josh,
I tried that CREATE TABLE statement in my MySQL database (version
4.1.12), and it gave me the following error:
ERROR 1005 (HY000): Can't create table
'./myproject/registrant.frm' (errno: 150)
I removed the "ENGINE=InnoDB DEFAULT CHARSET=latin1", and it created
successfully. Then, when I ran "django-admin.py inspectdb", it
inspected correctly.
So maybe this has something to do with the engine? Strange...
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
