Calling My SQL Experts / AutoIT

[Ghost21]

First I don't want a UDF as thats keeping the Sql statements in the code and not in the database. This

is why I'm trying to pass the variable like I am.

Here I'm trying to pass the $DomainPC to the Database and get it to return anything..

Some indicator that it either sees it in the database or not.

$Recordset.open("call _RA2011_All_PCINFO ('@" & $DomainPc & "');", $Connection)
If $Recordset.RecordCount <> 0 Then
else
GUICtrlSetData($Edit, "Found New Device: " & $DomainPc & " on " & $Founddomain & @CRLF, 1)
$Connection.Execute("INSERT INTO PCData (DOMAIN,DEVICE) VALUES ('" & $Founddomain & "','" & $DomainPc & "')")
EndIf

This is the routine I have setup in the Mysql Database

-- --------------------------------------------------------------------------------

-- Routine DDL

-- Note: comments before and after the routine body will not be stored by the server

-- --------------------------------------------------------------------------------

DELIMITER $$

CREATE DEFINER=`root`@`localhost` PROCEDURE `_ra2011_all_pcinfo`(IN DEVICEvar varchar(25))

BEGIN

SELECT Domain, DEVICE, IP, MAC, SerialNumber, Description, Tombstoned

FROM PCData

WHERE DEVICE = DEVICEvar;

END

[Ghost21]

Does anyone know how to call a Routine or a View in a MySQL DB from Autoit with a Variable ? PLEASE HELP..

Edited May 30, 2011 by Ghost21

[Zedna]

Look at ADO section in http://www.w3schools.com/

There are objects for this:

ADO Command and ADO Parameter

http://www.w3schools.com/ado/ado_ref_command.asp

http://www.w3schools.com/ado/ado_ref_parameter.asp

[Ghost21]

I would like to say that helped.. but it just confussed me more..

I can't believe that everyoen puts the code in the program and not in the database. Then pass the required variable

to the database and have it return the results..

[jchd]

There are reasons for that: stored procedure are not portable and only have little expressive power compared to applicative language(s).

So while it makes full sense to store as much SQL as needed in the form of constraints, triggers and views, stored procedure are much less of interest, should you have to move your DB from one engine to another.

Then having a procedure mapping a subselect is questionable. Can't you just use a subselect? You're turning the SQL engine into what it's not: an API for your application.