4 ms·
Well, in this case mysqljs pretty well fucked up the implementation here in that this sort of bug should never happen when using prepared statements, so I'd say
by hn_throwaway_99 5y ago
Well, in this case mysqljs pretty well fucked up the implementation here in that this sort of bug should never happen when using prepared statements, so I'd say it's worse than not having it at all, because it breaks the standard safety guarantees of prepared statements.
- Aeolun 5y agoThis implies that the alternative to using mysqljs is using prepared statements, which is most definitely not the case. The alternative for people using a library like this is to send plain queries to the db.