Will there be any way to debug stored procedures?
Also, will stored procedures be complied in any way, or are they always interpreted?

In the help file I saw info on the syntax for stored procedures, but didn't see anything about the machanics of creating and maintaining them.

Tom,

<< Will there be any way to debug stored procedures? >>

Not initially, no.  Although there will most likely be a statement for
logging messages or outputting debug strings, and that may help.

<<Also, will stored procedures be complied in any way, or are they always
interpreted? >>

They are always compiled actually, although any dynamic statements in the
stored procedures are compiled on the fly.

<< In the help file I saw info on the syntax for stored procedures, but
didn't see anything about the machanics of creating and maintaining them. >>

The documentation isn't even close to being done yet.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.

In Oracle if I submit a new stored procedure, it will tell me only if it compiled Ok or not.
If it couldn't compile, I can then ask Oracle to 'show errors'. This will let me know what line and column of the source a problem was found.

Do you envision something similar?

Tom,

<< In Oracle if I submit a new stored procedure, it will tell me only if it
compiled Ok or not. If it couldn't compile, I can then ask Oracle to 'show
errors'. This will let me know what line and column of the source a problem
was found. >>

EDB will tell you if there is a compilation error immediately, along with
the line and column of the error.  However, this does not apply to SQL
statements inside of the stored procedure because EDB executes all stored
procedures as dynamic statements.  See this thread for more information:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=19&msg=165&page=1#msg165

--
Tim Young
Elevate Software
www.elevatesoft.com

Would be nice if, additionally to the debugging of stored procedures
(SP), exists an optional version control for SP. Something like the
Version History that IBExpert manages with Interbase/Firebird database.

http://www.ibexpert.info/documentation/%20%203.%20Database%20Objects/%20%204.%20View/%20%201.%20New%20View%20_%20View%20Editor/%20%209.%20%20Version%20History/3055.html

IBExpert do that using a table that contains the versions for every
stored procedure in the database. When editing some stored procedures,
automatically a record of the stored procedure before modified is
inserted in that table. I don't know if this history information could
be stored in the elevatedb catalog or use the same way that IBExpert.

Regards.

Julio Saucedo

Julio,

<< Would be nice if, additionally to the debugging of stored procedures
(SP), exists an optional version control for SP. Something like the
Version History that IBExpert manages with Interbase/Firebird database. >>

Sure, that is possible to do at some point in the future.

--
Tim Young
Elevate Software
www.elevatesoft.com