Skip Menu |
 

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

Report information
The Basics
Id: 59550
Status: open
Priority: 0/
Queue: SQL-Translator

People
Owner: Nobody in particular
Requestors: danrumney [...] warpmail.net
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.11006
Fixed in: (no value)



Subject: DB2 Producer creates incorrect CHECK constraints
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 990
Download (untitled) / with headers
text/plain 990b
SQL-Translator-0.11006 # perl -v This is perl, v5.8.8 built for i386-linux-thread-multi # uname -a Linux L3X6996.ibm.com 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:58:38 EDT 2010 i686 i686 i386 GNU/Linux The SQL::Translator::Producer::DB2.pm generates CONSTRAINTS incorrectly. 1) For users wishing to create a CHECK constraint, it expects to see the type set to the string 'CHECK_C'. However, ::Producer::Constants defines CHECK_C to be the string 'CHECK', so CHECK constraints cannot be made validly. 2) With this fixed, there is still a problem with CONSTRAINT production. IBM developerWorks shows the syntax diagrams: http://www.ibm.com/developerworks/data/library/techarticle/dm-0401melnyk/index.html However, the DB2.pm producer will generate CONSTRAINTs that do not comply with these diagrams, in particular CHECK constraints. I am more than willing to write this fix, I will need a little guidance on the checking in process, but the fix bit, I'm more than capable of completing.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-17367-1327569048-465.59550-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 1459
Download (untitled) / with headers
text/plain 1.4k
On Mon Jul 19 17:40:08 2010, dancrumb wrote: Show quoted text
> SQL-Translator-0.11006 > > # perl -v > This is perl, v5.8.8 built for i386-linux-thread-multi > > # uname -a > Linux L3X6996.ibm.com 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:58:38 > EDT > 2010 i686 i686 i386 GNU/Linux > > The SQL::Translator::Producer::DB2.pm generates CONSTRAINTS > incorrectly. > > 1) For users wishing to create a CHECK constraint, it expects to see > the > type set to the string 'CHECK_C'. However, ::Producer::Constants > defines > CHECK_C to be the string 'CHECK', so CHECK constraints cannot be made > validly. > 2) With this fixed, there is still a problem with CONSTRAINT > production. > IBM developerWorks shows the syntax diagrams: > http://www.ibm.com/developerworks/data/library/techarticle/dm- > 0401melnyk/index.html > > However, the DB2.pm producer will generate CONSTRAINTs that do not > comply with these diagrams, in particular CHECK constraints. > > I am more than willing to write this fix, I will need a little > guidance > on the checking in process, but the fix bit, I'm more than capable of > completing.
Sorry, your ticket appeared to drop through the cracks of our nonexistent development process. If you are still available to write a patch we will be more than happy to help you! best way to reach us is on irc (just be patient, we are not at our PCs 24/7 :) https://chat.mibbit.com/#sql-translator@irc.perl.org Looking forward to working with you, cheers!


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.