www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - mysql-native: Prepared statements: Direction and future

reply "Nick Sabalausky (Abscissa)" <SeeWebsiteToContactMe semitwist.com> writes:
I've posted (what basically amounts to an article) about my current 
thoughts on addressing Prepared's current downsides in the next release 
(v2.0.0), as well as a little bit of future direction of the lib.

Anyone interested in mysql-native's prepared statements (especially 
their interplay with connection pools) is encouraged to take a look and 
share any thoughts:

https://github.com/mysql-d/mysql-native/issues/95#issuecomment-357757013
Jan 15
parent reply "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Mon, Jan 15, 2018 at 01:30:42PM -0500, Nick Sabalausky (Abscissa) via
Digitalmars-d-announce wrote:
 I've posted (what basically amounts to an article) about my current
 thoughts on addressing Prepared's current downsides in the next
 release (v2.0.0), as well as a little bit of future direction of the
 lib.
 
 Anyone interested in mysql-native's prepared statements (especially
 their interplay with connection pools) is encouraged to take a look
 and share any thoughts:
 
 https://github.com/mysql-d/mysql-native/issues/95#issuecomment-357757013
A lot of what you discuss here is pertinent not only to mysql-native, but to (SQL) database bindings in general. I've been facing much the same questions in my own SQLite bindings, which are based on Adam Ruppe's sqlite.d. One of these days, we should draft up a "standard" API for SQL database bindings in D, so that implementations can benefit from a well thought out API design instead of rolling their own each time. T -- "If you're arguing, you're losing." -- Mike Thomas
Jan 15
parent Martin Nowak <code dawg.eu> writes:
On Monday, 15 January 2018 at 19:41:42 UTC, H. S. Teoh wrote:
 https://github.com/mysql-d/mysql-native/issues/95#issuecomment-357757013
I've added some thoughts. https://github.com/mysql-d/mysql-native/issues/95#issuecomment-358110156
 One of these days, we should draft up a "standard" API for SQL 
 database bindings in D, so that implementations can benefit 
 from a well thought out API design instead of rolling their own 
 each time.
I'd hope that sth. emerges from MySQL-Native which is one of the more usable APIs atm. I also like http://biozic.github.io/d2sqlite3/d2sqlite3.html but it follows MySQL-Natives bad example in that regard. This is the design for more complex prepared statements in Cassandra. https://docs.datastax.com/en/developer/java-driver/3.1/manual/statements/prepared/
Jan 16