Skip Menu |

This queue is for tickets about the SQL-Translator CPAN distribution.

Report information
The Basics
Id: 25791
Status: resolved
Worked: 1 min
Priority: 0/
Queue: SQL-Translator
People
Owner: Nobody in particular
Requestors: antilyrical [...] spamcop.net
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.08
Fixed in: (no value)

History Show all quoted text
  Mon Mar 26 01:24:44 2007 antilyrical [...] spamcop.net - Ticket created
Subject: does not recognize PostgreSQL ON_ERROR_STOP
\set ON_ERROR_STOP 1 \set ON_ERROR_STOP 0 \set ON_ERROR_STOP Those above three commands can show up in PostgreSQL .sql files. Most common is the first one I believe. when converting from PostgreSQL to MySQL, I get an error on that line that says "Invalid statement".
  Wed May 09 22:06:04 2007 jasonk [...] cpan.org - Correspondence added
On Mon Mar 26 01:24:44 2007, antilyrical@spamcop.net wrote: Show quoted text
> \set ON_ERROR_STOP 1 > \set ON_ERROR_STOP 0 > \set ON_ERROR_STOP > > Those above three commands can show up in PostgreSQL .sql files. Most > common is the first one I believe. > > when converting from PostgreSQL to MySQL, I get an error on that line > that says "Invalid statement".
\set is a command for the psql command-line tool (and pg_dump/pg_restore), it isn't SQL and there is no reason that SQL::Translator shouldn't throw an error for that. If you are going to feed the output of pg_dump to an SQL::Translator script, you should probably remove all the non-SQL stuff in the file first...
  Wed May 09 22:06:06 2007 The RT System itself - Status changed from 'new' to 'open'
  Thu Aug 13 12:02:33 2009 kclark [...] cpan.org - Correspondence added 1 min
I'm going to assume this is sufficiently addressed since "\set" is not SQL.
  Thu Aug 13 12:02:35 2009 kclark [...] cpan.org - Status changed from 'open' to 'resolved'