Ask HN: Has anybody built search on top of Anna's Archive?
289 points by neonate 6d ago 146 comments
Ask HN: Is there any demand for Personal CV/Resume website?
6 points by usercvapp 1d ago 16 comments
Show HN: TextQuery – Query CSV, JSON, XLSX Files with SQL
163 shubhamjain 57 5/5/2025, 4:59:15 PM textquery.app ↗
Other extensions include but aren't limited to: MySQL, AWS, Azure, Excel, Iceberg, JSON
https://duckdb.org/docs/stable/extensions/postgres.html
It's basically what you're building, but more low-level. Really cool, to be honest -- serves the same market too. Do you have any significant differentiator, other than charts?
In context of TextQuery: you can use tabs you can work on multiple queries. With Table editor you can edit multiple field values at once. During import, you can have better control over what the final table would look like (select/deselect columns, define data/time format etc.)
Again, it's a personal preference. Some people swear by psql, and some can't live without TablePlus/Postico.
It reminds me of Log Parser Studio [1] on Windows. Using SQL to query text and log files is a great idea.
[1] https://web.archive.org/web/20170710212920/http://gallery.te...
I can import into SQL Server but there's too much ceremony needed (column types, etc) for quick looks at data I'm going to answer a question about and then discard. After a quick look at TextQuery I'm running into the same issues (although TextQuery is just a couple of clicks instead of 5+). I was also seeing an error yesterday from associating XLSX files with TextQuery but that seems to have gone away today.
Questions: What file sizes have you tested?
What about a directory with similar CSV files - I have a use case where similar structure CSV, 2 TB data broken into 700 files. Instead of 1 large file. Would that work?
Yes, even DuckDB has UI now, but I didn't find it to my taste. There's no table view, filters are a bit weird, and not exactly keyboard accessible. TextQuery also has Visualize feature to quickly create charts and tabs to run things in parallel. Again, it's personal preference, but there are advantages in being a desktop-first app.
XLSX would be the same workflow with "save as" CSV and then push it into SQLite.
My personal take is, yes, it's possible in multiple other ways, but I just like having a well-designed GUI app do it for me. Just how TablePlus does for Database Management.
MSSQL/SSMS supports this with some fancy techniques.
> This wizard was created to improve the current import experience leveraging an intelligent framework known as Program Synthesis using Examples (PROSE). For a user without specialized domain knowledge, importing data can often be a complex, error prone, and tedious task. This wizard streamlines the import process as simple as selecting an input file and unique table name, and the PROSE framework handles the rest.
> PROSE analyzes data patterns in your input file to infer column names, types, delimiters, and more. This framework learns the structure of the file and does all of the hard work so users don't have to.
https://learn.microsoft.com/en-us/sql/relational-databases/i...
Powershell can query excel files in various ways and there's a module for native powershell excel work: https://www.powershellgallery.com/packages/ImportExcel/5.4.2
1 - https://github.com/turbot/steampipe
No comments yet
No comments yet
I suspect the vendor is going to regret that, further down the line.
Fairly common. JetBrains started that way too. Will they one day have a major version that's using a subscription model? Perhaps. But they will likely not regret this too much.
Where does it say that?
That is common and it is the model I use for my own software. But that isn't what I understood from their website.
Home page: "Pay Once, Use Forever. We hate needless subscriptions as much as you do. TextQuery comes with a perpetual license with free updates."
Pricing page: "Perpetual license Lifetime updates"
Which strongly implies every update is free, forever.
I hate the subscription model but I do recognize if they continously update the software, they'd like to get paid to do so.
Absolutely. Just make it clear.
Anyone who knows SQL sees dozens of problems immediately. What enforces data integrity? How do we know the records are NF1? How do we perform a join, or test existential quantification, without table names? How do we know all supposed "dates" are valid dates, and not my uncles ex-wife’s maiden name? How does one reference XML attributes from SQL?
The answer produced by SQL are only as good as the data they’re drawn from. The quality and internal consistency of those data are enforced by the DBMS. No amount of pretty graphs and syntax highlighting changes that. The effective of SQL depends on the knowledge of the practitioner. No tool changes that, either.
So I guess I can see how not having to do the conversion for quick one-time analysis could be beneficial.