Originally posted by Ben Nichols:
Roman,
In my assignment, there is nothing stating that the convert utility be in anyway tied to the rest of the program. As I read it the convert utility is a separate command-line utility used to prep a flat file into a database binary for the client server portion of the program to take as a command-line. If there was such a requirement, it would be simple but wasteful of resources to write the database out as a flat file on every change. Typical databases are never implemented this way. Imports and Exports are resource intensive, and they are generally manual or scripted activities performed on an as needed basis.
Originally posted by J. Adams:
I'm also doing Fly By Night.
Are you allowing the user to cancel a "reserve seats" operation? It could take a long time if someone else has a lock on the flight.
Are you making time outs on the locks? Without them, a client could grab a lock, quit, and make it impossible for anyone else to reserve seats on that flight.
Originally posted by Rao V Kuna:
Ben is absolutly perfect and I agree 100% with him. I have one question ? Are U considering data checks like 13:75 hrs while converting or just dumping whatever U find in the Text File ?
Originally posted by Ben Nichols:
The Data.class is designed to support any sort of database using text-only fields. My convert utility does not validate data, because the database does not have field types (i.e. char, int, string, date/time...). My requirements state that the convert utility should be easy to reuse for other projects. To me this means if you want to import a address book, or flat file ascii database of plane replacement parts, your convert utility should be able to handle it. Validating data is not possible unless the database supports field types, and the user is able to match imported fields to existing field types during the import process. For an easy to command-line utility, this would be very difficult. Note: (Paraphrase) The dataset may be modified for a clearly justified reason, and such changes should be kept to a minimum. (End Paraphrase) I took this blurb from the requirements to mean that one probably had to make modifications to the dataset to meet the requirements.
Originally posted by Rao Kuna:
Ben
Thanks very much. I have couple of questions which I could not come to conclusion.
1. What is the length attribute in FieldInfo object ? Is it length of the field in Bytes or length of the field in chars ? I am thinking it should be bytes but how can we define the length of the string field in bytes ?
2. Do we need add Record Number to the record details given in the ascii file.
Thanks
Originally posted by Ben Nichols:
The Length is in characters, which the Data.class stores as bytes. For the record number, you're on your own. There are comments in the Data.class file (under the find method) that suggest record number is the first field.
Mahesh
Originally posted by hegdemk:
I have doubt about Fly By Night assignment. Whether to include passenger information in the same file as the flight information binary file or in a diffrent file or not to include at all ?
[/B]
hegdemk
Michael Finney - "Always Striving To Serve You Better Every Day"
http://www.smilingsoftwaresolutions.com/
Michael Finney - "Always Striving To Serve You Better Every Day"
http://www.smilingsoftwaresolutions.com/
I carry this gun in case a vending machine doesn't give me my fritos. This gun and this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|