plpgsql commenting broken?
After quite a few hours of poring over my latest plpgsql dabbling, i found the error that caused import to barf, and I was a bit surprised, since the error was caused by a single apostrophe in a comment line
-- check if the row isn't available
[SQL thingie]
of course, i could avoid the problem by rewriting my comments to
-- check if the row is available
[SQL thingie]
but it seems to me, that commenting a line should cause the parser to ignore *everything* until the next newline?
regards,
Johnny Jørgensen
johnny@halfahead.dk
+45 6315 7328
After quite a few hours of poring over my latest plpgsql dabbling, i found the error that caused import to barf, and I was a bit surprised, since the error was caused by a single apostrophe in a comment line
-- check if the row isn't available
[SQL thingie]of course, i could avoid the problem by rewriting my comments to
-- check if the row is available
[SQL thingie]but it seems to me, that commenting a line should cause the parser to ignore *everything* until the next newline?
Yes, this has bitten me before, particularly in awk script where the
script is single-quoted. I don't know a good solution for this.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Import Notes
Reply to msg id not found: 200112041628470534.002ED906@mail.halfahead.dk=?ISO-8859-1?Q?from_=22Johnny_J=F8rgensen=22_at_Dec_4=2C_2001_04=3A28=3A47_p?==?ISO-8859-1?Q?m?= | Resolved by subject fallback