Hi John,
You had mentioned earlier in a reply to my post "Retrievel from disk",
1. Yes, the entire record is read to get the fields you want. Generally the record is smaller than the size of the data the drive will read anyway.
I did not quite understand the second sentence.
For instance, if our table has 4 fields,
DOCID, AUTHOR, KEYWORDS, DOCTEXT
of datatypes
varchar(100), varchar(100), varchar(100), varchar(4000)
and if I do, "select DOCID from tbldoc"
all the 4 fields comprising of the record will be retrieved?
And what about the drive reading more than the record?
Also, in Texis, varchar(100), does not stop us from putting data more than 100bytes into a field, i.e. we can put a 2K text into author. How does this affect the concept of a record.
If you can please elaborate it would be much appreciated.
Basically, we are trying to optimize on performance of pulling DOCID's from disk.
Thanks!!
You had mentioned earlier in a reply to my post "Retrievel from disk",
1. Yes, the entire record is read to get the fields you want. Generally the record is smaller than the size of the data the drive will read anyway.
I did not quite understand the second sentence.
For instance, if our table has 4 fields,
DOCID, AUTHOR, KEYWORDS, DOCTEXT
of datatypes
varchar(100), varchar(100), varchar(100), varchar(4000)
and if I do, "select DOCID from tbldoc"
all the 4 fields comprising of the record will be retrieved?
And what about the drive reading more than the record?
Also, in Texis, varchar(100), does not stop us from putting data more than 100bytes into a field, i.e. we can put a 2K text into author. How does this affect the concept of a record.
If you can please elaborate it would be much appreciated.
Basically, we are trying to optimize on performance of pulling DOCID's from disk.
Thanks!!