Query regarding update functionality in UI

[David Winters Junior]

Hi All,

I have a query regarding whether i should put update functionality in the UI i.e allow a user to update certain fields in the database via the GUI.

The Database layer interface provided by Sun contains the following signature and description of the update method

// Modifies the fields of a record. The new value for field n
// appears in data[n].
public void update(int recNo, String [] data)
throws RecordNotFoundException;

In the user interface requirements the following is specified:

The user interface for this assignment must satisfy the following criteria:
It must be composed exclusively with components from the Java Foundation Classes (Swing components).
It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
It must present search results in a JTable.
It must allow the user to book a selected record, updating the database file accordingly.
Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a framework that will support this with minimal disruption to the users when this occurs.


As you can see in the above user interface requirements there is no mention of providing functionality which allows the user to update a record/records in the UI however in the Data interface we must provide an implementation.

So finally my questions are:

1) Do I provide functionality to allow a user to update a record in the UI or more specifically fields of a specific record?

2) If i do allow the user to update records in the GUI then since there is no mention of what fields the user can update in the UI in the specification above, is it at my discretion which fields i allow the user to update? If so what have others done in this scenario?

Many thanks in advance.
David


P.S I am working on UrlyBird 1.3.1

[David Winters Junior]

Hi All,

I was jsut wondering if anyone had any thoughts on this issue or of there are doubts in the question i pose then please let me know and i can clarify.

Thanks,
David

[Roberto Perillo]

Howdy, David.

I'm also working on the URLyBird 1.3.1, and I won't provide these functionalities. I mean, I implemented all methods that the DBMain interface requests, but I'll never call the create() method or the delete() method. I'll only call the find() method (to perform full/and/or searches) and the update() method (to allow the user to book a record), updating only the customer ID field.

Have a good day, partner!
[ January 31, 2008: Message edited by: Roberto Perillo ]

[David Winters Junior]

Thanks for the clarification.

So just one more question did you provide any implementation within the create or delete methods even though the user does not have the ability to add a record or delete a record. In this way at least the method definition is implemeneted to allow the possibility for future use of these methods

thanks again,
David

[Roberto Perillo]

Hey my buddy.

Yes, I provided implementation to these methods. I'm also reusing deleted entries. And remember, no matter what's your design choice, always document it clearly, and you'll be fine!

Take care, friend.

[David Winters Junior]

cheers roberto once again
David

[rohan tiwari]

Hello,
I have also not provided create and delete fucntionalities in the UI.The only update done through UI is that of ownerId for booking or releasing.

I have provided implementations of create and delete.I have also reused deleted records.