Do you have a more complete stack trace of where this went wrong? The one you included originally was just the top level of the trace, showing the bsh script where whatever caused the problem was called.
This happens quite a bit actually with new databases where they have small changes that are either not backward compatible, or that just conflict with how the Entity Engine uses JDBC (which is a somewhat loose but often loosely implemented specification).
Anyway, these are usually really easy to fix. -David On Feb 23, 2008, at 1:04 PM, Enrique Ruibal wrote:
Problem solved, had to uninstall PostgreSQL 8.3 and reinstall 8.2.5, everything works fine now..I think there is an issue with the latest version, I regret it though since it was a little faster than 8.2.5 Thanks for the advice -Enrique -- View this message in context: http://www.nabble.com/Error-in-Inventory-Reports-from-trunk-build-%2B-PostgresSQL-8.3-tp15646237p15656503.html Sent from the OFBiz - User mailing list archive at Nabble.com.
