Issue 60847 - Stored Proc Support
Summary: Stored Proc Support
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 103133 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-01-20 02:50 UTC by oiaohm
Modified: 2017-01-23 13:41 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description oiaohm 2006-01-20 02:50:51 UTC 
Most project I work on these days all interfacing with database has to happen
threw Stored Proc's.

Lack of support for this simple makes life harder than what it should be.

Stored Proc's can return one or many tables and other infomation.  OpenOffice
base need this feature.
Comment 1 oiaohm 2006-01-20 11:24:59 UTC 
Should have been more exact here.

We have Table View Querys all with direct interfaces to control and use.

There is nothing for Stored Procs.  They are just as much part of database's
these days.

From the GUI you should be able to call the Stored Procs and the Wizard for
creating Forms and Reports Should be able to handle these.

Permissions on Stored Procs in databases is critical.   Even allowing writing of
database dependent Stored Procs from Base makes base more usable.
Comment 2 marc.neumann 2006-01-26 12:58:46 UTC 
Hi,

I reassign this enhancement to the User Experience team for evaluating.

Bye Marc
Comment 3 stlman 2007-05-11 13:14:43 UTC 
HSQLDB can use java classes and methods as stored procedures and triggers. Why
not store such classes in .odb files and use those files lika JARs?
Comment 4 stlman 2009-10-01 11:35:11 UTC 
In bug #103133 I propose including JDBC driver JARs in odb files.
Comment 5 oooforum (fr) 2017-01-23 13:41:54 UTC 
*** Issue 103133 has been marked as a duplicate of this issue. ***