On Tue, 21 Oct 2008, Bernhard Graf wrote:
Jess Robinson wrote:
You could patch SQL::Translator::Parser::DBIx::Class (in the dbic
dist package) to use the name = .. key in the column_info.. then you
could use as you first mentioned and deploy (which uses sqlt) would
work.
Maybe I could, so
Bernhard Graf wrote:
One common practice to avoid problems with reserved words in column (or
table) names is to prefix every name with an underscore.
Is there an elegant and working way in DBIC to accomplish this?
I already tried
__PACKAGE__-add_columns(
user = {
data_type =
Peter Rabbitson wrote:
Do not mutilate column names, but instead use your tools the way they
were intended to be:
http://search.cpan.org/~ash/DBIx-Class-0.08010/lib/DBIx/Class/Storage
/DBI.pm#quote_char
I know these options, but
- their values depend on the underlying RDBMS,
- AFAIR their
Bernhard Graf wrote:
Peter Rabbitson wrote:
Do not mutilate column names, but instead use your tools the way they
were intended to be:
http://search.cpan.org/~ash/DBIx-Class-0.08010/lib/DBIx/Class/Storage
/DBI.pm#quote_char
I know these options, but
- their values depend on the
