next »

[perkiset]

Sorry CScott - by change I meant to eliminate the original line 11 - the one that says "echo "MySQLi Resource Handle: [$my]... that line must be eliminated, it's what caused that problem. The lines you added (if ($my) echo...) are the replacements for it.

[cafescott]

Perkiset,

great news!  it worked this time.

sorry for not taking out that offending line 11.

I'm really grateful for the help.  I'm very, very happy that you took the time to set me straight.

regards,

Scott

[perkiset]

No worries CScott... so are you using the package now? Is all well?

Hope so,
/p

[cafescott]

Perkiset,

I've taken a quick look at it, but for the moment i'm doing something else.  I plan to work with it in a couple of days.

thanks,

[cafescott]

Perkiset,

i'm looking over the utility.  i'm also trying to learn how to write MySQL stored procedures.  (i know mssql quite well; hopefully it won't be that huge of a learning curve.)

thanks for all the help.

 

[perkiset]

No worries mate.

Given how it all works, it's a little funky at first - but I can assist as you start with it. One of the largest problems is that the error messages I receive when posting a faulty script *really* do not clearly outline what the problem is. I pass on exactly what I get, but that just doesn't help much.

Good luck and post as you get troubles. Love to help.

/p

[cafescott]

hmm....the interface is a little hard to grasp at once.  do you have documentation for it?

thanks,

[perkiset]

Not really... what's your question?

Starting with "Script Explorer" tab on top, select a database, then click "Procedures" and you'll be shown all the procedures on <that> database. Click the New icon to create a new procedure. The new procedure code will show up in the editor space on the bottom.

(Change the ratio of space by dragging the "knuckles" in the middle)

Modify the procedure so that the code in the middle simple says

select 'Hello World';

then click the save icon in the editor pane (at the right).

Click on the Command Prompt tab. Type "use [your database]" and press enter. It should respond with OK. Type "show tables" and you should see all your tables in that database. Assuming your first procedure was called "first" type "call first()" and press enter. You should see "Hello World."

If all that works, we're in pretty good shape and it will start getting easier from there.

[cafescott]

"Starting with 'Script Explorer' tab on top, select a database"

i don't see my database.  i see the 'script explorer' tab.  There's a box below it.  Below it is a refresh button.  I click on the refresh button, nothing happens.  I click on the 'script explorer' tab.  Nothing appears. 

the connection name is correct, seen in the top right underneath the version number.  However, i don't see my database name and/or don't see how to type it in.

thanks,

[cafescott]

Perkiset,

i just tried it again and suddenly i see the databases after all.  please ignore the last post.

thanks,

[perkiset]

Glad of that... sorry I didn't post sooner, but that was a huge problem

Glad you're on the way. Don't be afraid to post more, we'll get you there.

[cafescott]

Perkiset,

here's a new question.  i have a mysql database.  i used the phpMyIDE utility to successfully create a stored procedure.  it shows up in my list of procedures after i select the Mysql database from the box on the left.

now i'd like to call the stored proc to see if it works.  I go to the command prompt and try this:

>call MyProcName(1)   { the 1 is an input parameter.}

i get this back:
Error: No database selected.

so i try it again, this time using this notation:

>call MySQLDB.MyProcName(1) 

this time the error is:
Error: Table 'MySQLDB.MyTableName' doesn't exist.

However, the table does exist when I click on the database and then go into the Database Explorer.

Do permissions have to be set on the tables and stored procedures to get them to run in the Command Prompt?

thanks,

[perkiset]

Stored procedures are not global - they are connected to (your) database.

So assuming your database was named "mybase", then in the command prompt, you'll need to type "use mybase" all commands will then be sent with that database as the default.

Some essential commands:

• To see what database you're using, simply type "show use"
• to "un use" a database, type "use"
• to show your connections, type "show connections"
• to use another connection (if you have multiple connections) type "use connection [n]" (where n is the connection number)

This is important though - you might consider putting your database in front of table references in your stored procedure. You'd do this by saying something like "select * from mybase.contacts where true" or some such - that will make sure that the stored procedure knows (in what database) the table you're referencing is.

[perkiset]

You could, alternately, type "call mybase.myProcName(1)" and it would execute, PROVIDED the references inside the procedure pointed to database.table, rather than just table.

[cafescott]

cool.  i think it's working now.

thanks for the help!