|Subject||Re: [Firebird-Architect] Re: Java Stored Procedures|
> Don't put Java source in the table. It's not useful to the database andDisagreed. Putting them in the database is great for ad-hoc development.
> there's no practical way to guarantee that it's in sync with the class
> blob. No compiler can find it there, and Java source files are normally
> handled by source code manager (cvs). Putting them in the database will
> drive everyone nuts.
If you can save your Java source and the Firebird Java plugin attempts
to compile it, return errors etc, this would be excellent, and pretty much
the same as the current PSQL Stored Procedures.
Now, if you decide on a final version of the source code, archive it in a
IMO, being able to do a bit of Java code changing without having a Java
compiled installed - locally - would be a good thing.
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Database development questions? Check the forum!