This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In my requirement, I only required to provided the search based on user input of name and/or location, but I also providing the search criterion based on user input of specialties and rates. Not sure if need to remove them. Guys, any idea? Just wonder if just leave it there good or not? I knew that no extra point on this additional feature.
hesitating because: (1)codes are there, don't want to change anymore (2)search based on specialties and rates may get error since no fully test there. Just some simple test. If error came out in this part, I sure will lost mark. Am I doing that stupid thing like moving a rock and hit my own feet. That is not worthy right?
I interpreted that line from my B&S slightly differently; I believe it means I must either allow the user to list all the records, or just those where (name.startsWith(searchTerm) || location.startsWith(searchTerm)) is true. I base this on the following extract from the interface I was required to implement:
I've also included support for searching across all fields.
McFinnigan? Never heard of him. Nobody here but us chickens...<br /> <br />SCJP for Java 1.4<br />SCJD for Java 5.0
Joined: Dec 15, 2005
thanks for your reply. Yes, my assignment also mention should providing user search on all records. I have implemented this by providing a separate button to allow user to list/view all the records. This is my understanding of "It must allow the user to search the data for all records". Is my understanding right?
You have find functionality described in user interface section AND find() in DB interface section. These don't fit together. Try to draw the picture.
- Not all methods are going to be used in the final application by your users. (But are nice for testing purposes for yourself, like create() method). - All methods have to work in the final application.
It's a bit of a puzzle, because you would think the specs would be more clear described but they are not. It's like a prism in some ways this SCJD.
SCJP 1.4<br />SCWCD 1.4<br />SCJD <br />SCEA (new version) Work in progress...