Actually you can do it, it is tricky though. Below is my example, I
have used similar in many procedures when I want to variabl-ize (made up
word I know) table names. The same holds true for setting field values
or order/group by.
delimiter //
DROP PROCEDURE IF EXISTS TestSelect
//
CREATE procedu
I have had this same exact problem. It has forced me to use cancel when
it prompts for the table and input the SQL manually. Basically I connect
to the datasource and hit cancel to the next screen to allow me to enter
the SQL.
I would love to know why this happens as well.
David Norman
Wells F
Often times when my replication breaks, it is a quasi monumental task to
re-sync.
Luckily, my replication is occurring on a data warehouse, where the
tables represent each days worth of data. If replication fails, I can
usually, get replication back on track by fixing whatever occurs in the
data/.
Actually you can do it, it is tricky though. Below is my example, I have
used similar in many procedures when I want to variabl-ize (made up word
I know) table names. The same holds true for setting field values or
order/group by.
delimiter //
DROP PROCEDURE IF EXISTS TestSelect
//
CREATE procedur
Greetings,
I wanted to see if anyone else has found this problematic, or if
I just missed something. I upgraded from 5.0.2 to 5.0.3-beta on my Red
Hat AS3 platform. It appears everything was fine till I went to execute
my stored procedures, which were owned by root at the console, since
th
