Update:
I misread the question. Sorry. Looks like this new V8 stuff is to make Camelcase work when the objective is to not make Camelcase work. In that case maybe some lower "name" parameter other than v8 will do the trick?
------

This may not be of much help as I have almost no experience with this. The docs are pretty complicated. But look at naming. Something like naming => { ALL => 'v8', force_ascii => 1 } looks appropriate,

And also, see v8 discussion:

v8

(EXPERIMENTAL) The default mode is "v7", to get "v8" mode, you have to specify it in "naming" explicitly until 0.08 comes out. "monikers" and "column_accessors" are created using String::ToIdentifier::EN::Unicode or String::ToIdentifier::EN if "force_ascii" is set; this is only significant for names with non-\w characters such as .. CamelCase identifiers with words in all caps, e.g. VLANValidID are supported correctly in this mode. For relationships, belongs_to accessors are made from column names by stripping postfixes other than _id as well, for example just Id, _?ref, _?cd, _?code and _?num, case insensitively.

In reply to Re: DBIx: How to dump schema with underscores for table names instead of camel case? by Marshall
in thread DBIC: How to dump schema with underscores for table names instead of camel case? by nysus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":