Skip Menu |

This queue is for tickets about the SQL-Translator CPAN distribution.

Report information
The Basics
Id: 63123
Status: resolved
Priority: 0/
Queue: SQL-Translator
People
Owner: Nobody in particular
Requestors: gmcnaugh [...] grnoc.iu.edu
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.11006
Fixed in: (no value)

History Show all quoted text
  Thu Nov 18 15:39:12 2010 gmcnaugh [...] grnoc.iu.edu - Ticket created
Subject: Support for Cross Database Foreign Keys
Hello, I'm using RHEL 5 with MYSQL 5.074 and the newest release of SQL::Translator while I understand how this can increase complexity greatly I've tested and tried a couple of times to parse a simple schema with a cross database foreign key constraint. It ends up not recognizing the database name + table name and ends up breaking the processing. Removing the cross database foreign keys allows the schema to parse, but I was hoping to be able to use this tool to do a full diff between the current running schema and a target schema.
  Thu Nov 18 17:34:20 2010 gmcnaugh [...] grnoc.iu.edu - Correspondence added
From: gmcnaugh [...] grnoc.iu.edu
After further investigation, the problem was with cross database foreign key constraints with this pattern: FOREIGN KEY `local_column` references `database`.`table` (`column`) translating them to: FOREIGN KEY `local_column` references `database.table` (`column`) made them fully functional. just something to be aware of, I suppose. On Thu Nov 18 15:39:12 2010, gmcnaugh wrote: Show quoted text
> Hello, > > I'm using RHEL 5 with MYSQL 5.074 and the newest release of > SQL::Translator > > while I understand how this can increase complexity greatly I've > tested and tried a couple of > times to parse a simple schema with a cross database foreign key > constraint. It ends up not > recognizing the database name + table name and ends up breaking the > processing. > > Removing the cross database foreign keys allows the schema to parse, > but I was hoping to be > able to use this tool to do a full diff between the current running > schema and a target schema. >
  Sun Feb 27 11:32:29 2011 ribasushi [...] leporine.io - Correspondence added
Apparently figured out by submitter.
  Sun Feb 27 11:32:30 2011 The RT System itself - Status changed from 'new' to 'open'
  Sun Feb 27 11:32:30 2011 ribasushi [...] leporine.io - Status changed from 'open' to 'resolved'