Use prepared statements #80

Open
opened 2020-08-06 16:54:34 +00:00 by gburd · 0 comments
gburd commented 2020-08-06 16:54:34 +00:00 (Migrated from github.com)

Wherever possible we should avoid parsing SQL.

We should also consider, after getting this working in the simple cases, whether it's better to loop over a prepared statement 300 times rather than to compose a 999-var SQL string and parse it.

Note that prepared statements will need to be closed at the appropriate time, and should ideally be lazily created as needed to avoid impacting time-to-open.

Wherever possible we should avoid parsing SQL. We should also consider, after getting this working in the simple cases, whether it's better to loop over a prepared statement 300 times rather than to compose a 999-var SQL string and parse it. Note that prepared statements will need to be closed at the appropriate time, and should ideally be lazily created as needed to avoid impacting time-to-open.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/mentat#80
No description provided.