This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

db.db and data conversion

 
Hung Tang
Ranch Hand
Posts: 148
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm just starting on SCJD and having difficulties getting started. Mainly I am having problems understanding how to use db.db. In particular, I don't know how to extract the information from it (the file is encoded) I looked at the Data class but can't seem to understand what it is doing. I'm kind of lost! (I know somewhere in the data class that it is doing data conversion on the database file) Can someone give me some pointers as to how to get a better understanding on how to use db.db file for this assignment? I know a lot of things are being done for you in the data class but maybe I am overlooking something.
Thanks
 
Hui Chen
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Basically, every field contains two attributes which are the field name and field length.
In my case, I just created a Data instance and used getFieldInfo() to retrieve the information about the structure of the data.
Hope this will help!
 
SungChan Park
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Following is copy from posted message
================================================
I was thinking that back when I began the project a good way of to
have approached (Which consequently is not how I did it but in
hindsight) the creation of the proj would be to go
1. Data Conversion Tool (-->Optional)
2. Depricated Methods
3. findCriteria()
4. Create a Data Interface
5. Create the Implementation of Interface ( Lock, book, thread,... )
6. RMI server
7. RMI client
You don't even need to think about FBN until this point. This would
keep you on course for your versatility.... Up until the GUI all
your code should be generic, It should'nt matter what DB your
running. Any db specific code should be kept out of the proj until
you've reached your GUI, even then your GUI could be dynamically
created based on another class which evaluates the db.
8. GUI & Table
9. Java Doc
10. Documentation
================================================
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic