I never use any data controls/classes in Delphi but TQUERY - this gives me
complete control over the SQL statements. Special db classes (databound
controls) like TTABLE and TSTOREDPROC have internal SQL statements for their
methods, which may or may not be the best/optimal for a particular database.
And you only discover which it is (optimal SQL or not) when the app is in
production and you get very irate users because of bad performance. Same
applies to VB programs - we only used snapshots and execsql and stayed away
for the other db objects.
I suggest using TQUERY only. You can also write a little stored proc wrapper
for TQUERY that is Oracle specific/optimised. That's why I love Delphi - if
you want to create a new class it's very easy. :-)
regards,
Billy
I have had success using the TSTOREDPROC component. The way to get
Delphi to see the stored procedure is to set up a synonym within Oracle
for the stored procedure.
Mike Hall
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet
CREATE OR REPLACE PACKAGE xxxx AS
PROCEDURE x2(vcInput IN VARCHAR2) AS
BEGIN
...
END;
END;
CREATE OR REPLACE PROCEDURE w_x2(vcInput IN VARCHAR2) AS
BEGIN
xxxx.x2(vcInput);
END;
This is a reliable workaround.
Billy Verreynne wrote:
> Magnus S. Petersen wrote in message
> <68um57$2jr$2...@news1.inet.tele.dk>...
create or replace package body xxxx as
procedure x2