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

Key: COR-663
Type: Bug Bug
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Critical Critical
Assignee: Unassigned
Reporter: Vidyadhar Nirantar
Votes: 0
Watchers: 0
Operations

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

Object vanishes when another object is saved to db

Created: 29/May/07 02:25 PM   Updated: 18/Jul/08 02:57 PM
Component/s: Local
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: Not Specified
Time Spent - 0.33h
Time Spent: 0.33h
Time Spent - 0.33h

File Attachments: 1. Java Source File AdapterTest.java (5 kb)
2. Java Source File AdapterTest.java (4 kb)

Environment: db4o 6.1, jdk 5, setup as for bug: COR-662
Issue Links:
Related
 

Resolution Date: 02/Jun/07 02:40 PM
First Response Date: 30/May/07 01:44 PM
Labels:
Participants: Richard Liang, Rodrigo B. de Oliveira and Vidyadhar Nirantar
Number of Attachments: 2
Number of Comments: 4


 Description  « Hide

A FieldNames object vanishes from the database after another PersistentEntry object is set.

The problem needs the same setup as for bug: http://tracker.db4o.com/browse/COR-662

A simple test program (AdapterTest.java) is attached. Just debug through the
AdapterTest#save() method. Place 2 breakpoints at positions highlighted in the test program.
Check contents of the db using ObjectManager at the two breakpoints.
The FieldNames object, that was earlier saved, is not seen later.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Vidyadhar Nirantar - 29/May/07 02:25 PM

Test case attachment

Richard Liang - 30/May/07 01:44 PM
Assist Persistent with Greg

Rodrigo B. de Oliveira - 02/Jun/07 02:37 PM
Modified version that dumps FieldNames instances to stdout for easy checking.

Rodrigo B. de Oliveira - 02/Jun/07 02:40 PM
I cannot reproduce the described behavior. I have attached a modified version of AdapterTest which dumps all FieldNames instances to stdout at the indicated source locations.

I get the following output:

<Output>

NO FieldNames in DB
02/06/2007 11:34:30 com.j_spaces.sadapter.GenericPA.Db4oPersistentAdapter initContext
INFO: END InitContext()
02/06/2007 11:34:30 com.j_spaces.sadapter.GenericPA.Db4oPersistentAdapter createClassTable
INFO: Class SA_DIRECTORY table created
02/06/2007 11:34:30 com.j_spaces.sadapter.GenericPA.Db4oPersistentAdapter insert
INFO: ***** Entered insert() SA_DIRECTORY
PUT A BRKPOINT HERE. CHECK FIELDNAMES OBJECT IN DB USING OBJECT MANAGER
*** DUMP BEGIN ***
[com.j_spaces.sadapter.GenericPA.FieldNames@228a02]
*** DUMP END ***
 fvalues len 1 names len 1
02/06/2007 11:34:30 com.j_spaces.sadapter.GenericPA.Db4oPersistentAdapter insert
INFO: Insertion of SA_DIRECTORY successfull
PUT A BRKPOINT HERE AND CHECK AGAIN USING OBJECT MANAGER. IT HAS VANISHED
*** DUMP BEGIN ***
[com.j_spaces.sadapter.GenericPA.FieldNames@228a02]
*** DUMP END ***
*** DUMP BEGIN ***
[com.j_spaces.sadapter.GenericPA.FieldNames@228a02]
*** DUMP END ***
02/06/2007 11:34:30 com.j_spaces.sadapter.GenericPA.Db4oPersistentAdapter closeContext
INFO: Database Closed

</Output>

The FieldNames instance with identity 228a02 has clearly not vanished.