Also adding a trailing semicolon to the "around" example. This way, it better agrees with the information in Manual::FAQ.
Luckily reason prevailed and $@ was left alone during DESTROY time, the complexity (mnost of it compiled away) is no longer needed More historic info can be found here: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/DBIx-Class-Historic.git;a=blob_plain;f=useful_guard_objects.html;h=4678884
review with -w, lots of reindentation
…1073ac) MySQL is unable to figure out it needs a temp-table when it is trying to update a table with a condition it derived from that table. So what we do here is give it a helpful nudge by rewriting any "offending" subquery to a double subquery post-sql-generation. Performance seems to be about the same for moderately large sets. If it becomes a problem later we can always revisit and add the ability to induce "row-by-row" update/deletion instead. The implementation sucks, but is rather concise and most importantly contained to the MySQL codepath only - it does not affect the rest of the code flow in any way.
It really does not belong in ResultSet.pm, but we do not have an API either. Take a first stab at a sketch, DQ will need to wrangle it to completion.
…on pending View the patch with -w, lots of reindentation
In the process join the notabs/eol tests into one file, and tighten the WS checks even more
This will stop things constantly getting out of sync
We *do not* yet turn on FK checking in sqlite - many tests will need tweaking
This fixes maint/gen_schema erroring out after 75d3bdb
Mainly remove a number of unused @_ unpackings, and remove the hideous _resolved_attrs_copy pessimizer
Instead of recalculating the data slice positions on every loop, we do it only once during the "proto bind" generation. This is because even though all bind values can and will change (even ones supplied via \[ ... ]), their number will always remain constant.
…er connecting This way a user does not have to worry about the particular DBI/DBD being loaded before accessing its constants
Original deprecation was put in place almost 2 years ago
and run the passing tests as real tests.