Bug #17582 for DBIx-DBSchema: DBIx::DBSchema::DBD::mysql column definitions

Fri Feb 10 16:09:17 2006 Guest - Ticket created

Subject:

DBIx::DBSchema::DBD::mysql column definitions

The software doesn't parse the column definition correctly. For instance, if the "Type" field contains the following: varchar(16) binary The length field is parsed as '16)' and the binary value isn't collected at all. The length but is fairly trivial to fix by changing the second capture group in the regex: $_->{'Type'} =~ /^(\w+)$?([^)]+)?$?( unsigned)?$/i ===========================^^^^^ The other issue is more difficult because it doesn't appear to support any extra data after the length and before the null/extra values.

Tue Oct 10 16:09:04 2006 ivan-pause [...] 420.am - Taken

Tue Oct 10 16:09:18 2006 ivan-pause [...] 420.am - Status changed from 'new' to 'open'

Wed Jun 27 22:15:36 2007 ivan-pause [...] 420.am - Correspondence added

From:

ivan-pause [...] 420.am

fixed in CVS, will be in 0.33, thanks! On Fri Feb 10 16:09:17 2006, guest wrote: Show quoted text

> The software doesn't parse the column definition correctly. For > instance, if the "Type" field contains the following: > varchar(16) binary > > The length field is parsed as '16)' and the binary value isn't

collected Show quoted text

> at all. The length but is fairly trivial to fix by changing the

second Show quoted text

> capture group in the regex: > > $_->{'Type'} =~ /^(\w+)$?([^)]+)?$?( unsigned)?$/i > ===========================^^^^^ > > The other issue is more difficult because it doesn't appear to

support Show quoted text

> any extra data after the length and before the null/extra values.

Thu Jun 28 22:02:01 2007 ivan-pause [...] 420.am - Status changed from 'open' to 'resolved'