"Chris Hilton" <[EMAIL PROTECTED]> writes:
> I see a few possible candidates in there the parser might not handle (in my
> WAG descending order of likelihood):
> REFERENCES `orolixPrizeManager`.`EcommerceOrder`
> COMMENT='RV transaction confirmation information (cell card purchase)'
That was it, COMMENT. Yanking it makes sqlt work.
> then update the grammar in Parser/MySQL.pm to handle your problem areas and
> submit your changes to the list here as a patch.
How to? I looked and looked at it, even tried running GUD on it, and
still have no idea on how does it work.
I found about table_options, and @options, but never found a list of
words it would accept.
I did found, in the description of MySQL syntax in the initial
comments to MySQL.pm, that it says:
or COMMENT = "string"
But the correct thing would be:
or COMMENT = 'string'
--
Leandro Guimarães Faria Corcete DUTRA +55 (11) 9406 7191 (cel)
Administrador de (Bases de) Dados +55 (11) 2122 0302 (com)
http://br.geocities.com./lgcdutra/ +55 (11) 5685 2219 (res)
BRASIL mailto:[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
sqlfairy-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlfairy-developers
