I've run across problems like this when writing parsers. The way I would do it is to liberalize the grammer and leave the checking of the ident to a later processing stage. For instance, I would probably use something like: 
ident : IDENT | INDENT_QUOTED | ident '.' IDENT | ident '.' IDENT_QUOT
+ED ;

[download]
and not have the grammar distinguish between table_ident, column_ident and database_ident. The checking of the proper kind of ident can be done later. This approach also generally makes it easier to recover from errors.

Update: The reduce-reduce conflict is this: when trying to parse a column_ident and the current input token is ident with look-ahead of ., the following reductions are possible: 

  database_ident -> ident # i.e. column_ident -> ident '.' ident '.' i
+dent
  table_ident -> ident    # i.e. column_ident -> ident '.' ident

[download]
One solution would be to reverse the recursion: 
database_ident: ident ;
table_ident: ident | ident '.' database_ident ;
column_ident: ident | ident '.' table_indent ;

[download]
Then when the look-ahead is '.' the grammar knows exactly what production to try to complete.

In reply to Re: (OT) Yapp rules and resolving reduce/reduce errors by pc88mxer
in thread (OT) Yapp rules and resolving reduce/reduce errors by dragonchild

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.