With Oracle, console output from System.out.println() statements will be written to trace files in the Oracle UDUMP destination directory.

Author: Suresh Payankannur (http://www.jguru.com/guru/viewbio.jsp?EID=288054) Question originally posed by Alex Chaffee PREMIUM (http://www.jguru.com/guru/viewbio.jsp?EID=3 By default, they will go to the console where the tomcat is started. You have to modify the startup scripts to redirect them to appropriate files. See Tomcat Mailing List for a discussion on how to redirect the System.out and System.err.

In the proc table of the mysql system database. However, you should not access the tables in the system database directly. Instead, use SHOW CREATE FUNCTION to obtain information about stored functions, and SHOW CREATE PROCEDURE to obtain information about stored procedures. See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information about these statements. You can also query the ROUTINES table in the INFORMATION_SCHEMA database - see Section 22.

We don't use stored procedures since they will result in a non-portable application. Our design allows, however, for stored procedures to be added elegantly--all you need to do is to provide an alternate Data Access Object that plugs into the application architecture and makes stored procedure calls. These are essentially a performance optimization that are particular to a specific application and its deployment environment.

Normally when we compare two objects we use the fundamental equals(Object) method. Conceptually, the equals method "belongs" to the objects you are comparing and returns a boolean to indicate whether they are passed a reference to themselves. Its not obvious why you would choose to make that comparison in the constructor of another class, which may only return a reference to the new instance, not a simple boolean response.

When starting the Forex Day Trading system software, the Java Console may appear. This is normal and is used to observe the incoming and outgoing messages. If you do not wish to see this simply close the window. If you do not want the Java Console to appear, from the Program menu select Java Plug-in Control Panel and disable the "Show Java Console" checkbox. Click on Apply to save changes.

The console output was redirected because in STAF 2.4.4 we changed the way JVMs for STAF Java services (such as STAX) output all of their stdout/stderr data (including the output of <script>print...</script> since that is being written to the JVM's stdout). All of the output that was formerly in the console output should now be in the JVMLog file. The file is located at: {STAF/DataDir}/lang/java/jvm/JVM Name/JVMLog.

Yes. For a database named dbname, use this query on the INFORMATION_SCHEMA.ROUTINES table: SELECT ROUTINE_TYPE, ROUTINE_NAME FROM INFORMATION_SCHEMA.ROUTINES WHERE ROUTINE_SCHEMA='dbname'; The body of a stored routine can be viewed using SHOW CREATE FUNCTION (for a stored function) or SHOW CREATE PROCEDURE (for a stored procedure). See Section 13.5.4.8, "SHOW CREATE PROCEDURE and SHOW CREATE FUNCTION Syntax", for more information.

Unfortunately, the official specifications are not freely available (ANSI makes them available for purchase). However, there are books - such as SQL-99 Complete, Really by Peter Gulutzan and Trudy Pelzer - which give a comprehensive overview of the standard, including coverage of stored procedures.

Not in MySQL 5.1. We intend to implement the SQL standard SIGNAL and RESIGNAL statements in a future MySQL release.

MySQL implements HANDLER definitions according to the SQL standard. See Section 18.2.8.2, "DECLARE Handlers", for details.

Yes, standard actions carried out in stored procedures and functions are replicated from a master MySQL server to a slave server. There are a few limitations that are described in detail in Section 18.4, "Binary Logging of Stored Routines and Triggers".

Yes, creation of stored procedures and functions carried out through normal DDL statements on a master server are replicated to a slave, so the objects will exist on both servers. ALTER and DROP statements for stored procedures and functions are also replicated.

MySQL records each DML event that occurs in a stored procedure and replicates those individual actions to a slave server. The actual calls made to execute stored procedures are not replicated. Stored functions that change data are logged as function invocations, not as the DML events that occur inside each function. Yes. Because a slave server has authority to execute any statement read from a master's binary log, special security constraints exist for using stored functions with replication.