wood burning stoves 2.0*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Remove a record or not?? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Remove a record or not??" Watch "Remove a record or not??" New topic
Author

Remove a record or not??

Hanna Habashy
Ranch Hand

Joined: Aug 20, 2003
Posts: 532
hi guys:
My instructuon for Bagittie & Scraper says that when I create a new record, I can possibly reuse a deleted entry. Hence, reusing a deleted entry is an option and not a requirment. In my design, I don't reuse a deleted entry. My reason is that this deleted entries can be used later on for data mining, and statistical information. From my work experiece with RDB, I got used to not delete anything from the database. Every bit of information can be helpful lataer on.
Do you think my reaon is justifiable, or should I go ahead and change the implementaion?


SCJD 1.4<br />SCJP 1.4<br />-----------------------------------<br />"With regard to excellence, it is not enough to know, but we must try to have and use it.<br />" Aristotle
Philippe Maquet
Bartender

Joined: Jun 02, 2003
Posts: 1872
Hi Hanna,

when I create a new record, I can possibly reuse a deleted entry. Hence, reusing a deleted entry is an option and not a requirment


I interpreted "possibly" as "when/if possible" (when such a deleted entry exists in the database), but I remember that a few native English-speakers here (including Jim Yingst) had another interpretation: "possibly" meaning "perhaps", you'd have the choice of implementing or not such a reuse of deleted entries. So your choice seems to be justifiable.

Regards,

Phil.
Hanna Habashy
Ranch Hand

Joined: Aug 20, 2003
Posts: 532
Here is the sentence as appeard in my instructions. Can some native speakers comment on the meaning

Creates a new record in the database (possibly reusing a deleted entry).

Does it mean that it is an option to use a deleted entry, or it means when possible use a deleted entry.
Either way, it doesn't make diferences to me. Personnaly, I prefere not to delete any entries, but I got to do what the requirments asks me to do.
thanks
[ May 17, 2004: Message edited by: Hanna Habashy ]
Andrew Monkhouse
author and jackaroo
Marshal Commander

Joined: Mar 28, 2003
Posts: 11404
    
  81

Hi Hanna,

I seem to recall the "discussion" that Phil is referring to. From memory one of the possible outcomes was that those of us whose native tongue is English seem to spend far too much time looking at the possible meanings in words rather than just going for a simple solution .

But for what it's worth, I take the "possibly reusing a deleted entry" to mean that it is at the implementer's discretion.

Or to put it another way, if I were writing the instructions, and I wanted you to reuse the space, then I would have writen that particular instruction as "reusing a deleted entry if possible".

I think you are on safe ground with the decision not to reuse deleted entries as you have justified your decision - as long as you document that decision you should be fine.

Many commercial databases work in a similar manner - for performance reasons, they usually do not try and reclaim space in the middle of transactions, rather waiting until the database is idle or waiting until explicitly told to reclaim space.

Regards, Andrew


The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
Hanna Habashy
Ranch Hand

Joined: Aug 20, 2003
Posts: 532
Thanks Andrew for your reply.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Remove a record or not??
 
Similar Threads
Database key
B&S: Booking a changed or replaced record.
NX: 5 problems about Data.java
Bodgitt & Scarper - Database Record Numbering
About create new record number for URLyBird