Prepared Statement builders #1968
tychobrailleur
started this conversation in
Dev
Replies: 1 comment
-
I'm not the big SQL expert. But as I understand it, the prepared statements have a performance advantage when they are often reused since the parsing step is only done one time. As far as I understand is the hsqldb already a kind of in memory database - so doubling the data into caches won't give a great benefit but requires a lot of extra memory space!? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am doing some refactoring on the database side of things, for the sake of adding unit tests & integration tests, and I had a question around prepared statement builders (i.e.
DBManager.PreparedStatementBuilder
): my understanding of their primary intent is to cache them so that they can be reused. Is that a fair thing to say?If that's the case, I am wondering of making this easier to manage, and possibly also looking at ways to cache the data rather than retrieving directly from the DB. That's something I am currently investigating.
Beta Was this translation helpful? Give feedback.
All reactions