Skip Menu |

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

Report information
The Basics
Id: 128064
Status: open
Priority: 0/
Queue: DBIx-Class

People
Owner: Nobody in particular
Requestors: joshr-cpan [...] joshr.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.082841
Fixed in: (no value)



Subject: Support for DBD::MariaDB
I just hit a big warning in DBIC about DBD::MariaDB which says (abbreviated): 'DBIx::Class::Storage::DBI::_warn_undetermined_driver(): This version of DBIC does not yet seem to supply a driver for your particular RDBMS and/or connection method ('MariaDB').' ... DBD => "DBD::MariaDB", DBD_VER => "1.10", DBIC_VER => "0.082841", ... Attached is the full error message info.
Subject: dbic-mariadb-error.txt
DBIx::Class::Storage::DBI::_warn_undetermined_driver(): This version of DBIC does not yet seem to supply a driver for your particular RDBMS and/or connection method ('MariaDB'). While we will attempt to continue anyway, the results are likely to be underwhelming. Please upgrade DBIC, and if this message does not go away, file a bugreport including the following info: { DBD => "DBD::MariaDB", DBD_VER => "1.10", DBIC_DRIVER => "DBIx::Class::Storage::DBI", DBIC_DSN => sub { package Dancer::Plugin::Database; use warnings; use strict; _load_db_settings() unless $settings; my($dbh, $cfg) = Dancer::Plugin::Database::Core::database('arg', $_[0], 'logger', \&Dancer::Plugin::Database::_logger, 'hook_exec', \&Dancer::Plugin::Database::_execute_hook, 'settings', $settings); $settings = $cfg; return $dbh; }, DBIC_VER => "0.082841", DBI_VER => "1.642", SQL_CURSOR_COMMIT_BEHAVIOR => "2 (SQL_CB_PRESERVE)", SQL_CURSOR_ROLLBACK_BEHAVIOR => "2 (SQL_CB_PRESERVE)", SQL_CURSOR_SENSITIVITY => "0 (SQL_UNSPECIFIED)", SQL_DATA_SOURCE_NAME => "DBI:MariaDB:database=jstock_test;host=db1.xab.com;port=3306", SQL_DBMS_NAME => "MariaDB", SQL_DBMS_VER => "05.05.6000", SQL_DEFAULT_TXN_ISOLATION => "2 (SQL_TXN_READ_COMMITTED)", SQL_DRIVER_NAME => "DBD/MariaDB.pm", SQL_DRIVER_ODBC_VER => "03.51", SQL_DRIVER_VER => "01.10.0000", SQL_EXPRESSIONS_IN_ORDERBY => "Y", SQL_GROUP_BY => "3 (SQL_GB_NO_RELATION)", SQL_IDENTIFIER_CASE => "4 (SQL_IC_MIXED)", SQL_IDENTIFIER_QUOTE_CHAR => "`", SQL_MAX_CATALOG_NAME_LEN => 64, SQL_MAX_COLUMN_NAME_LEN => 64, SQL_MAX_IDENTIFIER_LEN => 64, SQL_MAX_TABLE_NAME_LEN => 64, SQL_MULTIPLE_ACTIVE_TXN => "Y", SQL_MULT_RESULT_SETS => "Y", SQL_NEED_LONG_DATA_LEN => "N", SQL_NON_NULLABLE_COLUMNS => "1 (SQL_NNC_NON_NULL)", SQL_ODBC_VER => "03.80", SQL_QUALIFIER_NAME_SEPARATOR => ".", SQL_QUOTED_IDENTIFIER_CASE => "3 (SQL_IC_SENSITIVE)", SQL_TXN_CAPABLE => "3 (SQL_TC_DDL_COMMIT)", SQL_TXN_ISOLATION_OPTION => "0x0000000F (SQL_TXN_READ_UNCOMMITTED SQL_TXN_READ_COMMITTED SQL_TXN_REPEATABLE_READ SQL_TXN_SERIALIZABLE)", } DBIx::Class::Storage::DBI::sql_maker(): Your storage class (DBIx::Class::Storage::DBI) does not set sql_limit_dialect and you have not supplied an explicit limit_dialect in your connection_info. DBIC will attempt to use the GenericSubQ dialect, which works on most databases but can be (and often is) painfully slow. Please file an RT ticket against 'DBIx::Class::Storage::DBI' at t/020-schema.t line 30
Subject: Re: [rt.cpan.org #128064] Support for DBD::MariaDB
Date: Thu, 20 Dec 2018 00:44:35 +0100
To: bug-DBIx-Class [...] rt.cpan.org
From: Peter Rabbitson <ribasushi [...] leporine.io>
On 12/20/2018 12:37 AM, Josh Rabinowitz via RT wrote: Show quoted text
> Wed Dec 19 18:37:25 2018: Request 128064 was acted upon. > Transaction: Ticket created by JOSHR > Queue: DBIx-Class > Subject: Support for DBD::MariaDB > Broken in: 0.082841 > Severity: Normal > Owner: Nobody > Requestors: joshr-cpan@joshr.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=128064 > > > > I just hit a big warning in DBIC about DBD::MariaDB which says (abbreviated): > > 'DBIx::Class::Storage::DBI::_warn_undetermined_driver(): This version of DBIC does not yet seem to supply a driver for your particular RDBMS and/or connection method ('MariaDB').'
Indeed. I will look at shipping an updated version before the end of the months for this ( though I would definitely recommend DBD::mysql over DBD::MariaDB, but this choice is often preempted by a ton of external concerns )
I also hit this problem yesterday, so still persists. I managed to "fix" installing DBD::mysql, but support for DBD::MariaDB would be nice as it's indeed an easier installation sometimes (i.e. on some versions of MacOS installing DBD::mysql is half a nightmare ;-)). Thanks!