8

I'd like to use . to call sql script from inside a stored proc like so...

delimiter ///
create procedure append_procedure()
BEGIN
\. test.sql;    
END; ///
delimiter ;

I'm getting a "failed to open 'test.sql;' " error when I run it this way. I've also tried ! but then I get a permission denied error. However, I can't eliminate the ; or the whole thing is broken. Is there a way around this?

What am I doing wrong?

Bill Karwin
  • 538,548
  • 86
  • 673
  • 828
Yevgeny Simkin
  • 27,946
  • 39
  • 137
  • 236

2 Answers2

5

There is a set of commands that are builtin to the mysql client. They're documented under "mysql Commands." These include DELIMITER, SOURCE, HELP, CONNECT, USE, QUIT, etc.

The \. (or SOURCE) command is one of these builtins. You can't execute these builtin commands programmatically, nor from within a stored procedure.

It'd be like trying to run a UNIX shell builtin from a C program using execl().

A different analogy might be in a web browser, where you can type in special requests like "about:" that are handled by the browser app itself; these don't result in any HTTP request to a remote web site.

Also, it wouldn't help if you could source a script from within a stored procedure, because the script itself likely contains a bunch of commands that are mysql client builtins, and thus cannot be run by the stored proc.

See also my answers to these related questions:

Community
  • 1
  • 1
Bill Karwin
  • 538,548
  • 86
  • 673
  • 828
0

If you're on Sql Sevrer 2005 you can use the xp_cmdshell command.

http://msdn.microsoft.com/en-us/library/ms175046(SQL.90).aspx

Or

http://www.sqlservercentral.com/articles/Administering/scriptscheduling/450/

matt_dev
  • 5,176
  • 5
  • 33
  • 44
  • 1
    but i think he wants it for mysql – Gulzar Nazim Feb 13 '09 at 22:37
  • yeah, I'm tied to mySQL unfortunately. – Yevgeny Simkin Feb 15 '09 at 23:39
  • 1
    @GeniaS. I highly doubt the 3K to 15K license for Microsoft SQL Server is worth the capability of calling a script from a stored procedure... (and, having used MS SQL Server even more than MySQL but being experienced with both: there aren't any other features that are worth the price tag, or the requirement to run on an expensive Windows server OS) – MER Jan 11 '16 at 20:22