[Bug #3615] EOEntity fetchSpecification not addable

[nobody]

=================== BUG #3615: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3615&group_id=99

Changes by: David Ayers <d.ayers@inode.at>
Date: Wed 05/14/2003 at 23:40 (Europe/Vienna)

            What     | Removed                   | Added
---------------------------------------------------------------------------
            Category | None                      | gdl2
           Bug Group | None                      | Bug
          Resolution | None                      | Fixed
         Assigned to | None                      | ayers
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
a: Yes, we also initialize the fetchSpecification dictionary lazy.
b: Yes the should be, and the NSDictionary has been changed to a 
NSMutableDictionary

Thanks again!




=================== BUG #3615: FULL BUG SNAPSHOT ===================


Submitted by: dlatt                   Project: GNUstep                      
Submitted on: Wed 05/14/2003 at 21:19
Category:  gdl2                       Severity:  5 - Major                  
Bug Group:  Bug                       Resolution:  Fixed                    
Assigned to:  ayers                   Status:  Closed                       

Summary:  EOEntity fetchSpecification not addable

Original Submission:  One cannot add an EOFetchSpecification to EOEntity:
1. The method is now named
-addFetchSpecification:named:
it should be named
-addFetchSpecification:withName:

2. 
a. EOEntity's _fetchSpecificationDictionary is not initialized in EOEntity's 
-init, so when calling addFetchSpecificatin:withName:, it is still nil.
b. It is initialized when the EOEntity is read from a property list, but then 
it is initialized as an NSDictionary (not mutable), so setObject:forKey: 
doesn't work in addFetchSpecification:withName:.

Don't know for a.: if the dictionary should be initialized in -init or in 
addFetchSpec... if it is still nil there
for b.: if an entity read from a property list is supposed to have addable 
fetch specifications.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/2003 at 23:40       By: ayers
a: Yes, we also initialize the fetchSpecification dictionary lazy.
b: Yes the should be, and the NSDictionary has been changed to a 
NSMutableDictionary

Thanks again!



CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3615&group_id=99