Re: Database record format that encourages optimal retrieve(read, search, etc) & store(write, sort, etc)

On Sunday, September 13, 2015 at 4:23:50 AM UTC-4, seim..._at_gmail.com wrote:
> Hi,
>
> I am researching data that is optimal in how many
> distinct read operations are performed over a period
> of time and how many distinct write operations are performed
> over a period of time.

This isn't a theory question exactly. Once you start talking about record formats and reads and writes to files, you are talking about implementation.

>
> I have one example(bank account) which for generality is text only:
>
> Name: John Smith
>
> Age: 50
>
> Amount: + 1000
>
>
> Name: John Smith Jr
>
> Age: 31
>
> Amount: +100
>
> In the abobe example, an optimal write to the second record
> would consider
> the redundancy in the Name and Amount.

NO. John Smith Jr is not John Smith. The information is not Redundant!

>
> Likewise, while retrieving the record, an optimal read
> will not read all the bytes of the second record rather
> it will retrive the "Jr", & subtract a 0 from the Amount.

I'll just stop here and remind you:
Premature optimization is the root of all evil.

I think you are chasing the wrong solution. []

> My questions that are relevant to database theory are:
>
> i) What are good formats for data that encourage Optimal read
> and optimal writes ? Sacling from intra-records(1 bit) to
> intra-record(a few bytes) to entire databases.
>
>
> ii) Does database theory *have to* depend upon information theory or
> parallelism or other outside domain technologies for
> efficiency ?
>
> iii) In my example, what could the "Live Database" contain ?
>
> Sincerely,
> Seima Rao.
Received on Fri Nov 06 2015 - 16:19:39 CET