James K. Lowden, on Wednesday, February 26, 2020 11:55 AM, wrote... > > On Tue, 25 Feb 2020 12:02:24 -0500 > Przemek Klosowski <przemek.klosowski+sql...@gmail.com> wrote: > > > and I want to avoid storing repetitive data, so that the database > > should contain > > 10:32 12 > > 10:35 15 > > 10:39 13 > > 10:46 18 > > where only the earliest time with the unchanging value is stored. > > Be careful what you wish for. Usually "avoid storing" is a proxy for > some kind of intended use. Unless it's infeasible, it's usually better > to store everything, verbatim, as it arrives. Then you can present it > however you like, with nothing lost.
Fresh real-life-work experience... I was tasked to take data from a system and report on it, so, as I looked over the data I saw multiple entries, so I asked the client do you want to know if a set of data is repeated? "NO," said the client, "I only care for what new and fresh." Are you sure, I can see that there are repeated entries, and I can see different places where they are coming from, and how often, and... "NO!, I only care for what new and fresh." When I was going to show the reporting tool, she said, "By the way, this has how many times repeated records are coming in, and from where, correct?" I knew this was going to happened, so I had left a way to quickly make a few changes, re-imported the data, and was able to save the world. So, as James said, "I would keep everything and just show what you need." Maybe someday you want to know how many repeated entries happen in an hour, day, etc. Thanks. josé _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
