Tesseract.js VS Knex

What do you have against tesseract.js?

Are you able to use a OCR library in the browser? Here is one I found

But keep in mind, PDFs can be fully or partially made of images, and if you want text out of those, you will need to OCR them. There's tesseract.js for that.

Tesseract.js

YOu could try using tesseract.js to OCR the images. Though might be a challenge to figure out the times/days of the classes.

I've never used it - but Tesseract.js looks interesting. Perhaps you can use it as a foundation on which to build something like the AWS tool (which seems to work by overlaying an SVG over the top of the image, then manipulates that SVG when user clicks on a results tag to get the word/phrase's highlight box to display)?

I tried researching a little on this topic, so from what I understand to achieve this feature, I would need a library that supports Optical character Recognition (OCR) such as Tesseract.js or Google ML Kit to do it. However, I'm not too sure if these libraries will be supported on React Native apps.

It's definitely one of the best for on-the-fly OCR, but I think a server-based implementation using Google's Vision API would be way better. Definitely not mine, the AI used here is way beyond my skill level - link: https://tesseract.projectnaptha.com/

Knex.js

AdonisJS core team has created/maintains Lucid. It is a SQL query builder, and an Active Record ORM built on top of Knex.

Now, why not use an ORM? I've seen performance issues too many times with ORMs. I prefer writing my own SQL to avoid surprises. After all, I know the database schema and writing code for a specific purpose very often leads to better performance than generic code. ORMs have to support all kinds of database schemas. I only have to support mine. Having successfully used Knex.js in NodeJS (a popular query builder) in the past, I know writing SQL queries myself is not hard and provides very good performance.

Given the dynamic nature of the schema, we employ Knex, a query builder, for database access.

https://www.npmjs.com/package/knex - 779 issues

# related: https://github.com/knex/knex/issues/2354

This article will be focused on a security issue that I found in Knex and how to mitigate it, but I'll also talk briefly about the social aspects of this problem.

SQL is an old, irregular language to work with, but it is better known than HCL and SQL already has it's own Pulumi/CDK in the form of every ORM with introspection (like Javascript's Prisma, Python's Django, Go's XO etc) and QueryBuilder (LINQ, Knex, etc) in whatever programming language you prefer. You probably already know it.