On 29 янв, 10:47, Alexandre Conrad <[EMAIL PROTECTED]> wrote:
> Hello Max,
>
> AFAIR, I've had similar problems latelty when having a table with
> composite primary keys and running SQLite. I think Mike told me SQLite
> didn't support that. I'm no SQLite user, but I had this problem when I
> had to make a portable test case with SQLite in memory. If this can put
> you on track.
Well, I'm using MySQL 5. Table defs:
DROP TABLE IF EXISTS `dou_meetup_registrants`;
CREATE TABLE `dou_meetup_registrants` (
`id` int(11) NOT NULL auto_increment,
`meeting_id` varchar(20) NOT NULL default '',
`name` varchar(80) default NULL,
`email` varchar(80) NOT NULL default '',
`phone` varchar(24) default NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `meeting_id` (`meeting_id`,`email`),
CONSTRAINT `dou_meetup_registrants_ibfk_1` FOREIGN KEY
(`meeting_id`) REFERENCES `dou_meetups` (`id`) ON DELETE CASCADE ON
UPDATE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;
CREATE TABLE `dou_meetups` (
`id` varchar(16) NOT NULL,
`url` varchar(255) NOT NULL,
`created` timestamp NOT NULL default CURRENT_TIMESTAMP,
`is_active` tinyint(1) NOT NULL default '0',
PRIMARY KEY (`id`),
UNIQUE KEY `id` (`id`),
UNIQUE KEY `url` (`url`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
SQLAlchemy 0.4.2
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
