Skip Menu |
 

This queue is for tickets about the DBIx-Class CPAN distribution.

Report information
The Basics
Id: 47891
Status: resolved
Worked: 30 min
Priority: 0/
Queue: DBIx-Class

People
Owner: Nobody in particular
Requestors: ddascalescu+perl [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.08108
Fixed in: 0.08110



Subject: Cookbook entry for adding indexes incorrect about determining producer type
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 655
Download (untitled) / with headers
text/plain 655b
I'm trying to add an index to a table, and the index's definition depends on the underlying database type (support for retarded MySQL, to be more precise). http://search.cpan.org/perldoc?DBIx::Class::Manual::Cookbook#Adding_Indexes_And_Functions_To_Your_SQL claims that one can "change the index depending on the type of the database for which SQL is being generated" and gives this code example: my ($db_type = $sqlt_table->schema->translator->producer_type) =~ s/^SQL::Translator::Producer:://; However, $sqlt_table->schema->translator->producer_type returns 'CODE'. Is there another way to determine the underlying database in sqlt_deploy_hook?
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Charset: utf8
Content-Type: multipart/mixed; boundary="----------=_1247624277-25318-789"
Message-ID: <rt-3.6.HEAD-25318-1247624277-1115.47891-0-0 [...] rt.cpan.org>
X-RT-Original-Encoding: utf-8
Content-Length: 0
Content-Disposition: inline
Content-Type: text/plain
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 27
Attached a standalone test.
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Type: multipart/mixed; boundary="----------=_1247624277-25318-788"
Charset: utf8
Content-Length: 0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: iso-8859-1
Content-Length: 0
Content-Type: application/octet-stream; name="86sqlt_deploy_hook.rar"
Content-Disposition: inline; filename="86sqlt_deploy_hook.rar"
Content-Transfer-Encoding: base64
Content-Length: 1016
Download 86sqlt_deploy_hook.rar
application/octet-stream 1016b

Message body not shown because it is not plain text.

MIME-Version: 1.0
In-Reply-To: <rt-3.6.HEAD-25318-1247624277-1115.47891-0-0 [...] rt.cpan.org>
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Charset: utf8
References: <rt-3.6.HEAD-25318-1247624277-1115.47891-0-0 [...] rt.cpan.org>
Content-Type: text/plain
Message-ID: <rt-3.6.HEAD-25503-1250747669-1109.47891-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 124
Download (untitled) / with headers
text/plain 124b
This should be fixed in trunk by [1]. Please give it a spin. [1] http://dev.catalyst.perl.org/svnweb/bast/revision?rev=7344


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.