5 ms·

I don't know anything about this database, but this link did break the browser <back> button. Perhaps you can look into fixing that in a future release.

• TheTank 6y ago
  Thanks for the feedback, we'll look into it!
  • rkagerer 6y ago
    I tried these two: select * from trips; /* completed quickly */ select * from trips where tip_amount = 0.56; /* stalled */ Hope I didn't break anything ;-)
    • bluestreak 6y ago
      All good so far! Thank you for the feedback. Filter's are single threaded and not very fast. We will take them to the next level shortly
• sirffuzzylogik 6y ago
  Thanks for the feedback. A PR was created to fix this :) : https://github.com/questdb/questdb/pull/434 https://github.com/questdb/questdb/pull/434
  • cdubzzz 6y ago
    Interesting. This little bug comes up a lot on HN and is usually just that -- a bug. In this case, it seems that the "breaking" of the back button here was intentional based on the line comment[0]. What was the initial reasoning for that? [0] https://github.com/questdb/questdb/pull/434/files#diff-c9ec35dd22bf29a8a9ea540b1ab1aeb7L18 https://github.com/questdb/questdb/pull/434/files#diff-c9ec3...
    • bluestreak 6y ago
      the reason was grid scroll using touchpad on OSX, when you swipe the grid from left to right there is 50% chance of losing web console due to back button being triggered by the same motion.
      • cdubzzz 6y ago
        Ah, surprisingly good reason (:
    • lowdose 6y ago
      That's especially for people like you that love to find an easter egg.