Primary and foreign key specifications ignored during table creation

jeffdeville / penn-orchestra

Automatically exported from code.google.com/p/penn-orchestra

0 stars 0 forks source link

Primary and foreign key specifications ignored during table creation #4

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

When Orchestra creates a base table from an Orchestra schema file it ignores 
any information about keys in the specification.

Original issue reported on code.google.com by jwfro...@gmail.com on 22 Feb 2010 at 4:05

GoogleCodeExporter commented 8 years ago

Original comment by snd...@gmail.com on 22 Feb 2010 at 9:53

Added labels: Milestone-Release1.0, Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

Original comment by snd...@gmail.com on 1 May 2010 at 4:03

Added labels: Priority-Critical
Removed labels: Priority-High

GoogleCodeExporter commented 8 years ago

Lowering priority since this seems like this only effects an unusual use case, 
where instead of using Orchestra on an existing database, one is using 
Orchestra to create the database from scratch.

Original comment by jwfro...@gmail.com on 2 Jul 2010 at 8:19

Added labels: Priority-Medium
Removed labels: Milestone-Release1.0, Priority-Critical