DSQ VS Loggly

DSQ Reviews

Loggly Reviews

DSQ mentions (11)

• Tracking SQLite Database Changes in Git

  You might want to look at tsv-utils, or a similar project: https://github.com/eBay/tsv-utils (No longer maintained, but has links to lots of other projects). - Source: Hacker News / 6 months ago

• Command-line data analytics made easy

  SPyQL is really cool and its design is very smart, with it being able to leverage normal Python functions! As far as similar tools go, I recommend taking a look at DataFusion[0], dsq[1], and OctoSQL[2]. DataFusion is a very (very very) fast command-line SQL engine but with limited support for data formats. Dsq is based on SQLite which means it has to load data into SQLite first, but then gives you the whole breath... - Source: Hacker News / over 1 year ago

• Jq Internals: Backtracking

  > dsq registers go-sqlite3-stdlib so you get access to numerous statistics, url, math, string, and regexp functions that aren't part of the SQLite base. (https://github.com/multiprocessio/dsq#standard-library) Ah, I wondered if they rolled their own SQL parser, but no, I now see the sqlite.go in the repo and all is made clear. - Source: Hacker News / over 1 year ago

• Run SQL on CSV, Parquet, JSON, Arrow, Unix Pipes and Google Sheet

  I am currently evaluating dsq and its partner desktop app DataStation. AIUI, the developer of DataStation realised that it would be useful to extract the underlying pieces into a standalone CLI, so they both support the same range of sources. Dsq CLI - https://github.com/multiprocessio/dsq. - Source: Hacker News / over 1 year ago

• Xlite: Query Excel, Open Document spreadsheets (.ods) as SQLite virtual tables

  This is a cool project! But if you query Excel and ODS files with dsq you get the same thing plus a growing standard library of functions that don't come built into SQLite such as best-effort date parsing, URL parsing/extraction, statistical aggregation functions, math functions, string and regex helpers, hashing functions and so on [1]. [0] https://github.com/multiprocessio/dsq [1]... - Source: Hacker News / almost 2 years ago

Loggly mentions (1)

• “Print” Is the Only Debug Tool You Need

  Print works on Staging and Production: It’s not easy to work with debug tools when you’re dealing with code running on the server. On the other hand, print statements work there too. Even if you don’t have access to STDOUT, you can write statements to a file or send them to a logging server/service (e.g, Loggly). - Source: dev.to / almost 2 years ago