issues
search
huanshankeji
/
exposed-vertx-sql-client
Exposed on top of Vert.x Reactive SQL Client
https://huanshankeji.github.io/exposed-vertx-sql-client/
Apache License 2.0
5
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Support MySQL
#18
waste-of-kindergarten
opened
5 days ago
0
Support MySQL
#17
ShreckYe
opened
5 days ago
0
Split modules, completely overhaul the client creation APIs, and decouple PostgreSQL, our SQL DSL APIs, and our mapper SQL DSL APIs
#16
ShreckYe
closed
5 days ago
0
Support creating Vert.x SQL client queries without execution, for caching the prepared queries manually
#15
ShreckYe
opened
1 week ago
0
Depend on snapshots, adapt to the new Exposed DSL, split modules, and completely overhaul the client creation APIs
#14
ShreckYe
opened
1 week ago
0
Support DBs other than PostgreSQL
#13
ShreckYe
opened
1 week ago
1
Changes dependent on snapshots
#12
ShreckYe
closed
1 week ago
0
Deploy the API documentation to GitHub Pages with Dokka
#11
ShreckYe
closed
2 weeks ago
0
v0.4.0 release
#10
ShreckYe
closed
1 month ago
0
Develop dependent on snapshots
#9
ShreckYe
closed
1 month ago
0
Adapt to the new SELECT DSLs and remove a conflicting old `deleteWhereStatement` DSL
#8
ShreckYe
closed
1 week ago
1
Differentiate between the function names in `DatabaseClientSql.kt` and `DatabaseClientSqlWithMapper.kt`
#6
ShreckYe
opened
8 months ago
1
Rename the functions removing the "execute" prefixes in DML functions
#5
ShreckYe
closed
1 week ago
1
Hide the statement execution (CRUD/DML) APIs from Exposed
#4
ShreckYe
opened
1 year ago
0
Build queries without the redundant Exposed connection
#3
ShreckYe
opened
1 year ago
0
Integrate with ORM at compile-time
#2
ShreckYe
opened
2 years ago
0
Study the performance implications of generating SQLs every time for prepared queries
#1
ShreckYe
closed
1 week ago
2