Bugzilla Version 2.16.7
Bugzilla Bug 1790
  print bind values in the DEBUG log
     Query page      Enter new bug
Bug#: 1790   Platform:   Reporter: martin-fuchs at gmx dot net (Martin Fuchs)
Product:   OS:   Add CC:
Component:   Version:   CC:
Remove selected CCs
Status: CLOSED   Priority:  
Resolution: FIXED   Severity:  
Assigned To: werner dot guttmann at gmx dot net (Werner Guttmann)   Target Milestone:  
URL:
Summary:

Attachment Type Modified Status Actions
proposed patch patch 2004-11-19 15:34 none Edit
extended patch patch 2004-11-19 15:34 none Edit
also handle NULL values patch 2004-11-19 15:34 none Edit
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 1790 depends on: Show dependency tree
Show dependency graph
Bug 1790 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments:


Leave as CLOSED FIXED
Reopen bug

View Bug Activity   |   Format For Printing

Description: Opened: 2004-11-13 02:17

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'

------- Additional Comment #1 From Martin Fuchs 2004-11-13 02:18 -------
Created an attachment (id=767)
proposed patch

------- Additional Comment #2 From Martin Fuchs 2004-11-13 05:14 -------
Created an attachment (id=769)
extended patch

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

------- Additional Comment #3 From Martin Fuchs 2004-11-19 15:34 -------
Created an attachment (id=784)
also handle NULL values

------- Additional Comment #4 From Werner Guttmann 2004-11-22 02:14 -------
Patch applied as is.

------- Additional Comment #5 From Martin Fuchs 2004-11-22 11:36 -------
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?

------- Additional Comment #6 From Werner Guttmann 2004-11-22 12:43 -------
> 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.

     Query page      Enter new bug
This is Bugzilla: the Mozilla bug system. For more information about what Bugzilla is and what it can do, see bugzilla.org.
Actions: New | Query | bug # | Reports   New Account | Log In