11/9/2012 6:04:16 PM
will now print the SQL query (if available), for example:
33445 [main] WARN com.ning.billing.util.entity.dao.EntitySqlDaoWrapperInvocationHandler - Error during transaction for sql entity interface com.ning.billing.account.dao.AccountSqlDao and method test [SQL State: 42000, Vendor Error Code: 1064]
select t.record_id
, t.id
,
, t.account_record_id
, t.tenant_record_id
from accounts t
where t.tenant_record_id = ?
limit 1
;
The vendor message is still available when the exception is re-thrown:
java.lang.RuntimeException: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' t.account_record_id
, t.tenant_record_id
from accounts t
where t.tenant_record_' at line 5
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 5:31:08 PM
with Audited anymore, as all dao classes are
automatically audited now.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 5:27:07 PM
Use EntityDaoBase for AuditedAccountDao
* Use MockEntityDaoBase for MockAccountDao
* Fix SQL queries (no account_record_id for the accounts table)
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 5:22:46 PM
but quite useful, at least in the tests.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 4:28:43 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 4:26:01 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 4:15:59 PM
but quite useful, at least in the tests.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 4:06:05 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 4:04:33 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
11/9/2012 3:30:19 PM
into audit-rework
|
