typo
typo copied to clipboard
Typed Postgresql integration for Scala. Hopes to avoid typos
Builds on `seek`-support added in #100 ## Pagination with `ClientCursor` On top of `seek` I managed to write a completely generic pagination mechanism. It works for any query, including when...
these are generated in `Fields` objects so othey are accessible in DSL: ### generated boilerplate: ```scala def fkEmployee: ForeignKey[EmployeeFields, EmployeeRow] = ForeignKey[EmployeeFields, EmployeeRow]("humanresources.FK_JobCandidate_Employee_BusinessEntityID", Nil) .withColumnPair(businessentityid, _.businessentityid) ``` ### usage: ```scala...
for now you have to code a watch mode in your script, which is obviously not a great thing to demand of users
Probably because it is built with 3.4.0 now, causing forward compatiblity issues. In my case, it's not a big deal because I'm just running a scala-cli script but I wonder...
As of scala 3.4 there is no common subset for expressing supplying varargs without warnings, hence breaking the shared subset typo is written in. Once we're at it, I guess...
Hi, I have the following generator: ``` // remember to give the project a github star if you like it using dep "com.olvind.typo::typo:0.6.0" //> using scala "3.3.0" import typo.* //...
Initial port of java codegen for typo
ideally should have property tests for all supported column types, among many other things
The chatgpt pass made the text quite fluffy, and it's missing some details still