Hi,
I am trying to call a stored procedure using dhtmlxConnector. Is that possible?
How can I do something like …
$data->render_sql("CALL SomeStoredProcedure", "Id", "Field1, Field2");
Is that possible?
Hi,
I am trying to call a stored procedure using dhtmlxConnector. Is that possible?
How can I do something like …
$data->render_sql("CALL SomeStoredProcedure", "Id", "Field1, Field2");
Is that possible?
grab version 1.1
dhtmlx.com/x/download/regula … hp_dvl.zip
with it, you can use
$data->render_complex_sql("CALL SomeStoredProcedure", "Id", "Field1, Field2");
Awesome! Thanks!
Will this work with the dhtmlxScheduler?
Yep, all connector classes support such method
Thanks for the updates.
Just tried to use it …
At first glance, it didn’t seem to work. All that was returned were
/*
This software is allowed to use under GPL or you need to obtain Commercial or Enterise License
to use it in non-GPL project. Please contact sales@dhtmlx.com for details
*/
However, upon closer inspection, there xml was hidden below those comments and the browser doesn’t recognize the document as an xml document.
Will this affect the proper operation of the connector classes?
Just an observation that this might be due to the fact that the above mentioned comments were outside the <?php> tags in their respective .php files. Would you have a simple way of fixing it?
Updated package is available online, thanks for the problem report.
dhtmlx.com/x/download/regula … hp_dvl.zip
Thanks for the fix!
Are stored procedures also available for the coldfusion connector?
Hi. Unfortunately, coldfusion connectors currently do not support the stored procedures.
Hi,
Is not possible to pass parameters to a stored procedure?
With the 1.1 version fix with this SQLSrv
EXEC SDU_Portal_Extracto '111','2012','1','6'
render_complex_sql returns this error:
EXEC SDU_Portal_Extracto ‘111’,‘2012’,‘1’,‘6’
Invalid argument supplied for foreach() at C:\php\includes\connector\codebase\db_sqlsrv.php line 47
Done in 0.025470018386841s
Without the parameters it runs fine.
Thanks
Is the same SQL code works correctly while running through other tools?
The above error can occur if there was not dataset returned by the sql code.
You can enable logging and check log for the problematic operation - it may contain some extra details.