Rather than file a bug, I'd suggest you post it to the Class::DBI mailing list. Most people get their problems solved that way.

I'll keep the mailing list vs. bug report idea in mind. Speaking of the list, I just recently found a relevant thread covering my issue. It seems to be a case of a lack of tuits. I'll take another spin in the debugger to see if I can't find exactly where the problem is. If I can, I'll be submitting a patch.

Also, the complaint about not finding column "gid" makes me think that you might need to tell Postgres which tablespace or schema you are working in. It may be trying to use an internal table called "users" in the main Postgres tablespace.

That -- as was determined in another part of this thread -- was caused by incorrect quoting issues.

In reply to Re^3: Mixed-case column names breaking under Class::DBI by sintadil
in thread Mixed-case column names breaking under Class::DBI by sintadil

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.