[ANN] OrindaBuild 4.0 - Writes Java to access Tables, PL/SQL procedures,and Oracle SQL Statements

[ANN] OrindaBuild 4.0 - Writes Java to access Tables, PL/SQL procedures,and Oracle SQL Statements

Post by announc » Sat, 17 Jan 2004 05:55:25


What is OrindaBuild 4.0?
========================

OrindaBuild?is a utility that automatically writes Java?code to access
tables, stored procedures, packages, functions and sequences in Oracle?
databases. OrindaBuild also takes files containing SQL statements and
generates matching Java source files to run them. By automating the
tedious task of writing access code, it can dramatically improve
productivity. OrindaBuild also helps to reduce the time taken for Java
code to catch up with database design changes.

How does it work?
=================

OrindaBuild has a Swing GUI to choose Tables, PL/SQL?procedures or
files containing SQL statements. Specify the location for code
generation, add your comments and other configuration information and
click Generate. All the source you need is either created or ships with
the product. There is no runtime component and your code continues to
work when your license expires.

Design features:
================

Intuitive and straightforward - A Swing GUI lists existing database
objects and makes creating code trivial.

No mysterious runtime component - Everything is done with human readable
source code.

No precompilers needed - No requirement to use SQLJ.

Large object support - BLOBs, CLOBs and BFILE parameters can be treated
as java.io.File objects.

Pay-As-You-Go Licensing - OrindaBuild is available for periods ranging
from one month to a year. When the license expires you can maintain the
code by hand. Generated code does not stop working because your licence
has expired.

No Schema Changes - OrindaBuild does not create any additional database
objects such as Procedures or Tables.

Table Support:
===============

Persistance - Rows can be retrieved or modified using any valid Primary
or Unique key.

Navigation - Rows from related tables can be retrevied using methods
that follow the table's Foreign Keys.

PL/SQL Support:
===============

Cursor Support - Cursors can't be left open and are returned in a
spreadsheet like data structure.

Understands Oracle's privileges - Can call PL/SQL objects owned by other
users or referred to by Synonyms.

Support for BOOLEAN parameters - Can call PL/SQL procedures with BOOLEAN
parameters without having to create an additional procedure.

Support for records as parameters - Can call PL/SQL Procedures that have
%ROWTYPE, %TYPE, PL/SQL Package Record and Oracle Object Type Parameters
provided they don't have nested records.

SQL Support:
============

Simple user interface - The only thing users have to do is name and give
data types to parameters. This can be done with either the Java user
interface or by placing special comments after parameters in the SQL file.

Supports all legal SQL statements - OrindaBuild will make a runnable
Java class out of any file that containts a valid SQL statement

All query results can be cached - SELECT statements are turned into
classes which can cache query results

Compatible with SQL*Plus - OrindaBuild turns the '&' character into '?'
and removes surrounding quotes when reading SQL files. Files which are
runnable in SQL*Plus will turn into runnable Java source code without
modification.

Downloading OrindaBuild
=======================

Orinda Software's web site is located at: http://www.orindasoft.com/

A fully functional Version of OrindaBuild can be downloaded from:
http://www.orindasoft.com/public/
 
 
 

1. OrindaBuild 4.0 - Now provides DAO to run Oracle PL/SQL Procs fromJava...

2. Calling an Oracle PL/SQL procedure from MS SQL Server stored procedures

Hi,

I'm totally new to both Oracle and MS SQL Server - so please forgive
any vocabulary stupidities...

The scenario is as follows:
I want to transfer certain information from a database on a MS SQL
Server to a Oracle server. This should happen once a day.

I need the datatransfer to work in this manner:
1. A query is run on the SQL Server - resulting in X posts
2. Each post individually initiates a PL/SQL procedure located on the
Oracle Server, that ensures data is submitted correctly. This
procedure returns success true/false. The procedure needs various
fields from the post as parameters. - All posts are processed like
this.
3. Logging transfer-information on the SQL Server.

As you might have guessed - number 2 is the tricky part. I'm totally
lost here - don't know how to call a PL/SQL (I do have all the
information required for an ODBC).

An example would be really appreciated.

Sincerely
Ryan

3. PL/SQL Nested Table inside a SQL statement

4. from oracle (pl/sql) to sql server (t-sql)

5. MS Access 2002 SQL to Oracle 9 PL/SQL

6. DBD::Oracle accessing Global Temporary Tables in PL/SQL.

7. convert ms access sql staement to oracle sql statement

8. SQL Statement to retrive data from MS SQL and write into MS Access

9. SSIS Oracle error on an execute of PL/SQL procedure

10. Orphan REF cursor returned to VB.NET from Oracle PL/SQL stored procedure?

11. Is it possible to run an Oracle PL\Sql procedure within Excel?

12. US-TX-ORACLE, PL/SQL, TRIGGERS AND STORED PROCEDURE DEVELOPMENT

13. How to pass a boolean parameter to an oracle PL/SQL procedure

14. realistic cardinality for PL/SQL procedures in SELECT statements