Re: ZEOS 7.3 i StoredProc ... i wogóle

Article View: pl.comp.lang.delphi.bazy-danych

Article #82705

Back to pl.comp.lang.delphi.bazy-danych Previous Next

#82705

From: miab
Date: Fri, 07 Oct 2016 19:59

24 lines
1640 bytes

W dniu 2016-10-07 o 14:46, Morff pisze:
> Próbuję zaprząc ZEOSA do roboty z Oracle.
> I jakoś przy StoredProc nie chcą się automatycznie tworzyć parametry :
>
> prc.StoredProcName := schema_+'.'+package_+'.'+procname_;
> prc.prepare;
>
> no i prc.paramcount = 0
>

A u mnie taki zestaw instrukcji jak najbardziej kompiluje się, działa i 
daje sensowne wyniki:

ZStoredProc1.Close;
ZStoredProc1.StoredProcName:='ADQA_TESTBINDING';
Edit1.Text:=IntToStr(ZStoredProc1.Params.Count);
ZStoredProc1.Params[0].Value:=12.367;
ZStoredProc1.Params[1].Value:='zupa';
ZStoredProc1.ExecProc;
Edit2.Text:=ZStoredProc1.Params[0].AsString+' 
'+ZStoredProc1.Params[1].AsString;
ZStoredProc1.Open;

miab

Technical Details

Message-ID: <nt8v02$e7g$1@node1.news.atman.pl>

Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mail

References: <5a30eeb3-d080-4f78-952c-9aba4deda341@googlegroups.com>

Show Full Headers

Complete Article Headers

Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mail
From: miab <miwa14@wp.pl>
Newsgroups: pl.comp.lang.delphi.bazy-danych
Subject: Re: ZEOS 7.3 i StoredProc ... i wogóle
Date: Fri, 7 Oct 2016 21:59:48 +0200
Organization: ATMAN - ATM S.A.
Lines: 25
Message-ID: <nt8v02$e7g$1@node1.news.atman.pl>
References: <5a30eeb3-d080-4f78-952c-9aba4deda341@googlegroups.com>
NNTP-Posting-Host: 89-79-241-203.dynamic.chello.pl
Mime-Version: 1.0
X-Trace: node1.news.atman.pl 1475870530 14576 89.79.241.203 (7 Oct 2016 20:02:10 GMT)
X-Complaints-To: usenet@atman.pl
NNTP-Posting-Date: Fri, 7 Oct 2016 20:02:10 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
In-Reply-To: <5a30eeb3-d080-4f78-952c-9aba4deda341@googlegroups.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reply to Parent Message