Am Dienstag, den 16.02.2010, 11:52 +0100 schrieb Fernand Vanrie:
> So far i found a lot of things not working with Stored Procedures, but
> finaly :-) i got a sort of workaround for a Stored Procedure on MySql
> with parameters.
>
> SUB TESTstoredprocedurecall
> oBaseContext = CreateUnoService("
So far i found a lot of things not working with Stored Procedures, but
finaly :-) i got a sort of workaround for a Stored Procedure on MySql
with parameters.
SUB TESTstoredprocedurecall
oBaseContext = CreateUnoService("com.sun.star.sdb.DatabaseContext")
oDB = oBaseContext.getByName("mysql_nat
Drew ,
You says : "sure there is some access to the stored procedures with the
current implementation but it isn't yet ready to take full advantage them"
I know you are a bussy man and always prepared to help, but can you
explaines a bit more and gives us some hints from wath can already been
d
Marc Santhoff wrote:
Am Samstag, den 13.02.2010, 18:22 +0100 schrieb Marc Santhoff:
And just here i am lost: how works this registering of the
parameters ?
Dunno, my assumption was that it is not strictly necessary ... I tink
someone else has to answer this question.
A quick l
Am Samstag, den 13.02.2010, 18:22 +0100 schrieb Marc Santhoff:
> > And just here i am lost: how works this registering of the
> parameters ?
>
> Dunno, my assumption was that it is not strictly necessary ... I tink
> someone else has to answer this question.
A quick look into chapter 8 of the HSQ
Am Samstag, den 13.02.2010, 13:41 +0100 schrieb Fernand Vanrie:
> Marc, (the other one :-))
>
> Thanks for your interest, i will test your "preparedstatement" code a
> soon i maded some "test" storedprocedures on a MySQL base.
> But i am still troubled about the use like it is is writen in the DE
Marc, (the other one :-))
Thanks for your interest, i will test your "preparedstatement" code a
soon i maded some "test" storedprocedures on a MySQL base.
But i am still troubled about the use like it is is writen in the DEV guide.
Ther they say to use a "Preparecall" :
The method prepareCall(
Am Freitag, den 12.02.2010, 15:42 +0100 schrieb Fernand Vanrie:
> Marc,
I'm another one, but maybe I can give a little help. ;)
> Its even worse ,after further investigation i found no code (API +
> basic) to run a stored procedure with parameters.
> So I would be very happy i someone could giv
Am 12.02.10 16:35, schrieb Frank Schoenheit, Sun Microsystems Germany:
> Hi Marc,
>
>> Can the
>> internal SQL parser be changed to accept statements like
>>
>> SELECT * FROM function(:parameter) ?
>
> Probably, yes (but Ocke has a saying in this, he has deeper insights in
> the parser implement
Hi Marc,
> Can the
> internal SQL parser be changed to accept statements like
>
> SELECT * FROM function(:parameter) ?
Probably, yes (but Ocke has a saying in this, he has deeper insights in
the parser implementation).
Feel free to submit an issue.
Ciao
Frank
--
- Frank Schönheit, Software
Marc,
Its even worse ,after further investigation i found no code (API +
basic) to run a stored procedure with parameters.
So I would be very happy i someone could give a hint :-)
thanks for any help
Fernand
you told : "That makes, in consequence, stored procedures unusable with
OpenOffice
> you told : "That makes, in consequence, stored procedures unusable with
> OpenOffice base".
Well, I probably need to refine that a bit, indeed: It makes stored
procedures unusable in OpenOffice base using the query editor.
>
> This is countrary to what the DEV guide tells us
>
> Stored
Marc ,
you told : "That makes, in consequence, stored procedures unusable with
OpenOffice base".
This is countrary to what the DEV guide tells us
Stored procedures are server-side processes execute several SQL commands
in a single step, and can be embedded in a server language for stored
> If we talking about "General users" it could been a good start to make
> StoredProcedures visible in the GUI before we adding bells like
> parameters etc
I would not call parameters to function calls "bells", I would call it a
necessity.
> Other users (who have acces to there own Databases
Am 12.02.10 08:29, schrieb Frank Schoenheit, Sun Microsystems Germany:
> Hi Marc,
>
>> Maybe a third mode could help here: Semi-Native SQL, where base would
>> only scan for parameter definitions using the : scheme.
>
> Hmm, don't like this idea too much. Basically, it would be completely
> intr
Frank , Marc
If we talking about "General users" it could been a good start to make
StoredProcedures visible in the GUI before we adding bells like
parameters etc
Other users (who have acces to there own Databases) do not need other
than Native Mode because they written already the Stored
Hi Marc,
> Maybe a third mode could help here: Semi-Native SQL, where base would
> only scan for parameter definitions using the : scheme.
Hmm, don't like this idea too much. Basically, it would be completely
intransparent to the user. This is not per se a bad thing :), but if
things are prone t
Frank,
>> I can, however, set the query editor
>> to native SQL mode, then the SQL code is passed as is to the database
>> backend and no error is output. But with native SQL mode, I loose the
>> possibility to have OpenOffice ask the user for parameters. I can only
>> use calls without paramete
Hi Marc,
> I can, however, set the query editor
> to native SQL mode, then the SQL code is passed as is to the database
> backend and no error is output. But with native SQL mode, I loose the
> possibility to have OpenOffice ask the user for parameters. I can only
> use calls without parameters.
Am 08.02.10 13:35, schrieb Fernand Vanrie:
> We uses also "Stored Procedures" on a Msql server To make all things
> work , we handles all user input (parameters calculatutions,
> translations etc...) with OO-dialogs and some macro's to create the SQL
> statements writen to please the ODBC driver
> SELECT * FROM acf_balance_all()
>
> To get the balance from only on account, you would use
>
> SELECT * FROM acf_balance('1000')
>
> ('1000' is the account number).
>
I'd guess the problem is the ability of DBA to bind columns for display.
That is, while postgres understands the columns wh
Marc ,
We uses also "Stored Procedures" on a Msql server To make all things
work , we handles all user input (parameters calculatutions,
translations etc...) with OO-dialogs and some macro's to create the SQL
statements writen to please the ODBC driver and the Msql server :-)
Good day
We de
Hello Marc Balmer,
It would be great if you could submit an issue and perhaps could add a
sample db dump (only with dummy data and one sample procedure) for a
test case. And assign it to me o...@openoffice.org.
Best regards,
Ocke
Marc Balmer wrote:
Good day
We develop point of sales (POS)
Good day
We develop point of sales (POS) applications using PostgreSQL as the
database backend. We thought it could be interesting for our customers
to access the database directly from OpenOffice Base to create their own
reports etc. But it turns out that OpenOffice Base and PostgreSQL are
not
24 matches
Mail list logo
