Fix exception on complex update/delete under a replicated setup
THIS COMMIT IS A HACK!!! The actual fix is migration of the logic to the
SQLMaker subclass and deal with it there. However the entire class hierarchy
is currently in flux, so go with the least invasive change until the storage
rewrite settles.
(cherry pick of da4a8fe7)
Peter Rabbitson
9 years ago
| 3 | 3 |
- Protect destructors from rare but possible double execution, and
|
| 4 | 4 |
loudly warn the user whenever the problem is encountered (GH#63)
|
| 5 | 5 |
- Fix updating multiple CLOB/BLOB columns on Oracle
|
|
6 |
- Fix exception on complex update/delete under a replicated setup
|
|
7 |
http://lists.scsys.co.uk/pipermail/dbix-class/2015-January/011903.html
|
| 6 | 8 |
- Fix hang in t/72pg.t when run against DBD::Pg 3.5.0. The ping()
|
| 7 | 9 |
implementation changes due to RT#100648 made an alarm() based
|
| 8 | 10 |
timeout lock-prone.
|
| 306 | 306 |
_parse_connect_do
|
| 307 | 307 |
savepoints
|
| 308 | 308 |
_sql_maker_opts
|
|
309 |
_use_multicolumn_in
|
| 309 | 310 |
_conn_pid
|
| 310 | 311 |
_dbh_autocommit
|
| 311 | 312 |
_native_data_type
|
|
| 362 | 363 |
# the capability framework
|
| 363 | 364 |
# not sure if CMOP->initialize does evil things to DBIC::S::DBI, fix if a problem
|
| 364 | 365 |
grep
|
| 365 | |
{ $_ =~ /^ _ (?: use | supports | determine_supports ) _ /x }
|
|
366 |
{ $_ =~ /^ _ (?: use | supports | determine_supports ) _ /x and $_ ne '_use_multicolumn_in' }
|
| 366 | 367 |
( Class::MOP::Class->initialize('DBIx::Class::Storage::DBI')->get_all_method_names )
|
| 367 | 368 |
)],
|
| 368 | 369 |
};
|