I've just finished some final cleanup and testing of Plisqin and am ready to call it "stable, but incomplete".
https://docs.racket-lang.org/plisqin/index.html Plisqin's semantics are similar to SQL but there are some key differences. Perhaps the most significant is that joins are values, not language constructs. Plisqin is incomplete in that it still lacks first-class Insert/Update/Delete support. However, it is easy to mix in arbitrary SQL pretty much anywhere you want, so this might not be a problem depending on your use case. With this release I will be taking a break from any major work on Plisqin. Bugfixes and small enhancements should be no problem though. If you decide to try Plisqin from source, be aware that a few tests will fail on Racket CS due to differences in the Printer. As long as your code does not depend on any printable representations it will be fine. A big "Thank You!" to everyone who has made the Racket ecosystem so great, and special thanks to everyone who helped me with my questions. - Ryan Kramer -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/24be7b61-3719-405b-9966-920fd55792aco%40googlegroups.com.
