Baron,
I am sourcing it. I do not know if that is the best way though.. I am
running the insert statement from a mysql prompt  in a linux/windows
machine.
My script has a single build script which sources other scripts.
build.sql
======
source ./ddl/useraccount/useraccountddl.sql
source ./mobchannel_db.sql
source ./ddl/usercontent/usercontentddl.sql
source ./ddl/userinfo/profilesddl.sql
source ./ddl/system/systemddl.sql
source ./ddl/shopping/retailitem.sql
source ./ddl/shopping/shoppingddl.sql
source ./ddl/rewards/userrewardsddl.sql
source ./ddl/location/locationddl.sql
source ./ddl/listing/listingddl.sql
===========================
I will cd into the directory which contains the sql (so that '.' gets
resolved) and do a mysql -u root -p and enter password and do a
mysql>use dbname;
mysql>source build.sql;

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near ')' at line 8.
But I do not know which sql does that, there are so many. I cannot scroll
the putty all the way also. I need to know other errors that might occur. Is
there any command by which I can see last run errors, like some errors that
are saved in the buffer. As I know this is the last sql statement that gets
executed.

On 10/5/07, Baron Schwartz <[EMAIL PROTECTED]> wrote:
>
> Arun wrote:
> > I have a large batch of insert sql statements, of which some of them are
> > failing. I want to know which one is failing exactly.
> > Is there anyway I can debug it  and which statement went wrong. I have
> only
> > 4 or 5 out of 200 statements that are failing.
> >
> It depends on how you're running the batch, and you didn't give us any
> information about that.  Are you doing something like this?
>
> mysql < batch.sql
>
> If so, try
>
> mysql --line-numbers < batch.sql
>
> This option may be enabled already.  Try running mysql --help | grep
> 'line-numbers' to see.  It's enabled by default on my machine:
>
> [EMAIL PROTECTED]:~$ mysql --help | grep 'line-numbers'
>    --line-numbers      Write line numbers for errors.
>    -L, --skip-line-numbers
> line-numbers                      TRUE
>
> Baron
>



-- 
Thanks
Arun George

Reply via email to