|
Re: [pm-h] complex data structure help: msg#00014lang.perl.perl-mongers.houston
11:31am, Paul Archer wrote: > > Maybe a simple format: > > filesystem user client-machine time-to-the-hour read written > > Then for every line, I check to see if I have an entry that matches the > first four parameters. If so, I add the number of bytes read or written. If > not, I create a new entry. Then I can sort by whatever field I want, and > limit my searches however I need to. > > Only that seems inefficient. Could I normalize that somehow? > > Paul > I talked this over with a coworker. He suggested one table each for users, client machines, and filesystems, just for lookups. Then one table for a combination of the three, and one table for timeperiods with the bytes written or read for each time period. I think that'll work...
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [pm-h] complex data structure help, Paul Archer |
|---|---|
| Next by Date: | Re: [pm-h] complex data structure help, Matt Sisk |
| Previous by Thread: | Re: [pm-h] complex data structure help, Paul Archer |
| Next by Thread: | Re: [pm-h] complex data structure help, Matt Sisk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |