History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CASTOR-927
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Werner Guttmann
Reporter: Martin Fuchs
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
castor

print bind values in the DEBUG log

Created: 13/Nov/04 02:17 AM   Updated: 19/Apr/05 10:53 AM
Component/s: JDO
Affects Version/s: 0.9.5.4
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File castor-1790-2.patch (3 kb)
2. Text File castor-1790-3.patch (3 kb)
3. Text File castor-1790.patch (2 kb)

Environment:
Operating System: All
Platform: All

Bugzilla Id: 1790


 Description  « Hide
This patch adds additional debug messages containing the value of bound
paramater values. The following example shows the format of the message:

1468 [main] DEBUG org.exolab.castor.util.SqlBindParser - Binding SQL parameter
value: ?1 = 'SALES'



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Martin Fuchs - 13/Nov/04 02:18 AM
Created an attachment (id=767)
proposed patch

Martin Fuchs - 13/Nov/04 05:14 AM
Created an attachment (id=769)
extended patch

This extended patch prints out also the type of the bind values.


Martin Fuchs - 19/Nov/04 03:34 PM
Created an attachment (id=784)
also handle NULL values

Werner Guttmann - 22/Nov/04 02:14 AM
Patch applied as is.

Martin Fuchs - 22/Nov/04 11:36 AM
OK, thanks.

To disable printing of this new debug messages while running the test suite,
you can insert the following into src\tests\log4j.xml:

<category name="org.exolab.castor.util">
<priority value="error" />
</category>

May be we could even insert one config entry for the complete org.exolab.castor
class hierarchy instead of the two existing ones for org.exolab.castor.jdo and
org.exolab.castor.persist?


Werner Guttmann - 22/Nov/04 12:43 PM
> May be we could even insert one config entry for the complete org.exolab.castor
> class hierarchy instead of the two existing ones for org.exolab.castor.jdo and
> org.exolab.castor.persist?
Agreed. I think we should use the level "error" or "warning". In addition, we
should use a pattern-layout consistently.