uh.. UNIQUE... DISTINCT... , On Tue, Sep 26, 2017 at 4:30 PM, Stephen Chrzanowski <[email protected]> wrote:
> > > On Tue, Sep 26, 2017 at 1:36 PM, Simon Slavin <[email protected]> > wrote: > >> >> >> My one concern in reading your post is how your dates are formatted. >> When putting your date fields into your SQL table you will have to ensure >> that dates are saved as a day number, or as text which naturally sorts into >> date order, e.g. YYYY/DD/MM. You should not expect SQL to sort text such >> as "19 October 16" correctly. >> >> Simon. >> > > @OP, Simon is dead on, however, the only correction and clarification to > that statement is you'll want (if required) to sort by YYYY/MM/DD, not > YYYY/DD/MM. > > Also, for deduplication, if you're executing one instruction, you can add > a UNIQUE clause after the SELECT, unless you've got other requirements that > make defines what a duplicate entry is, then you'd have to rely on your > software for those decisions. > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
