Is there a plan to support indexes?

[11]

Hi, first I just want to say I love where the project is heading. DenoDB is by far the most concise and easy to conform to ORM within the Deno ecosystem. This is a huge achievement for the project and the Deno community! I'd also love to help push this project further if there is an official roadmap that contributors can work towards

With that said, without knowing anything about future plans, I was wondering if there are at least intentions to support indexes in the near future?

I've done my own digging within the codebase and from what I can tell, supporting the index query doesn't seem like a huge undertaking - at least for SQL DBs (correct me if I'm wrong on this - I'm probably being a bit optimistic)

But the lack of indexes is really the only thing holding me (and probably others) back from wanting to use this for a production service

Thanks for a response in advance

[jcs224]

I think indexes are more of a concern for when the table as a whole is created or modified. This library is focused on being an ORM for existing data (although you can optionally create the table). You can add an index on table creation or after-the-fact with something like Deno Nessie, and the queries made by this library should take advantage of those indexes.

https://github.com/halvardssm/deno-nessie