That's a good point! Makes sense to just keep the generic one, and perpahs call it jdbc platform.
some things I rememeber when we implemented the generic one: 1 - It still depends on the wayang-jdbc-template for some key functionalities. So keeping only one would require careful refactoring 2 - The postgres one also supports join where as the generic one only supports project and filter 3- I'd suggest to benchmark the generic one against postgres one for postgresql db to make sure there is no compromise on functionality and efficiency. Best, Kaustubh On Sat, May 3, 2025 at 12:24 AM Zoi Kaoudi <zkao...@yahoo.gr.invalid> wrote: > Hello team, > I have the following question. Shall we retire the wayang-jdbc-template > module together with the postgres and sqlite3 platforms and keep only the > wayang-generic-jdbc one? > In the wayang-generic-jdbc normally one can provide any jdbc url so it's > kind of a superset of the other three modules in my understanding. We will > have to port the join operator there but it should not be hard to do that. > > Do you see any points in keeping all of them? It's kind of creating extra > effort in maintaining all of them imo. > Best > -- > Zoi
