On Fri, 2007-11-09 at 22:56 -0500, Hilmar Lapp wrote: > On Nov 9, 2007, at 10:38 PM, Ben Faga wrote: > > > It turns out that that is exactly what was happening already. The $1 > > was being blanked (as it should be) but the MySQL producer wasn't > > handling it properly (the postgres and oracle producers handled it > > just > > fine). > > > > I've modified the foreign key constraint name so that if it is > > blank, it > > will default to TABLENAME_fk (as opposed to being named "_1", "_2",... > > as it was doing). > > Not sure I understand correctly - did you make this change in the > parser (consumer)? > > What you say above sounds to me like the MySQL producer is broken > (and should hence be the one to be fixed), not the PostgreSQL consumer. > > -hilmar
Yes and exactly. I've committed the change in the MySQL producer. Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- sqlfairy-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlfairy-developers
