Why are sequenced queries and queries that deal with time periods so difficult to express in current RDBMS?

Share and Enjoy:
  • del.icio.us
  • Reddit
  • Facebook
  • Identi.ca
  • TwitThis

Related posts:

  1. Error Signaling: Exceptions and Error Values
  2. AgilePakistan.org
  3. RDBMS, thy end is nigh
  4. Time to switch over to Joda Time

2 Comments on 'Time based queries' read them below or add one

Subscribe to comments with RSS or TrackBack to 'Time based queries'.

  1. This is probably not even germane to what you want, but anyway, here’s my spur of the moment theory.

    SQL was constructed not be as expressive as possible but to be human readable by non-S.W. devs, and some functionality had to be left out of the language in order to facilitate this this design decision. Successive iterations of the language have brought it incrementally towards some level of completeness, with a concomitant increase in complexity.

    Basically, as far as I can tell SQL works with only atomic data elements (or “points”), not ranges or intervals (or “lines”). There’s no mechanism, that I remember offhand, to express an interval in SQL easily.

    Yuck. Just a guess…

    Senor Pablo - 14 Sep 06 at 4:48 am

  2. Agreed, sql was only designed or points not ranges, I want it to be more useful working with temporal data because I find myself working with time sequenced data quiet often.

    Shey's Rebellion - 14 Sep 06 at 4:08 pm

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search