With the native driver (ODBC or CTLIB for sybase) the print messages come up as information messages when they are sent.  JDBC moves those to the end as part of the warning chain.  (if you are debugging the old fashion way, print statements would tell you the state at a certain point before seeing the results after that point, but in JDBC they all come at the end)

what we do is when going through the warning chain for SQL Server and Sybase, we pull out the informational messages from the warning chain and display them as a result instead of as a warning.

o in RapidSQ:L/DBARtisan, "print 'test';" would be the same as "select 'test'"

in terms of output