PM wanted them. :-)
I mentioned we're a xAAS. (I'm not sure which one.) We support ETL using reusable bits of code and the database bits are really basic - L (select, lookup), T (mostly non-DB), and L (insert, update, merge, delete), plus a way to execute arbitrary code and occasional database-specific functionality like the specialized teradata <-> hadoop tools. To a large extent everything but the last item hide the SQL from the user. I haven't looked at that part of the code recently but I think at that abstraction layer it's using the information to create jOOQ Conditions, etc., in a DB-agnostic way. it's a classic Pareto (iirc) situation where 80% of the users can do everything they need with the bits that completely hide the SQL details and the rest can do use the safety valve that allows arbitrary SQL. It's far less limited than you might think if you move your complex logic into views. (I know it doesn't play well with caching but I think there's a lot to be said for keeping the java queries simple and leaving the hard stuff to someone who really knows the database and can create views and triggers to hide the details. If it's not something covered in a SQL 101 course start moving chunks into a view until it is. As a side benefit having one expert who knows all of the queries used will be able to do optimizations that a group of mid-level SQL people working on their individual problems can't.) I'm looking at a lower abstraction layer. By this point we have the query (either a sql string or a Query) and need to convert the data from the format used on the bus to the format used by the database and vice versa. I have nothing but a database connection, that query, and a Map. (Plus 8 dollars, a pack of cigarettes, and half a tank of gas. Or whatever the line was in the Blues Brothers....) On Tue, Mar 20, 2018 at 10:36 AM, Lukas Eder <[email protected]> wrote: > Oh, cool. Wow. What's the common denominator for all those databases? :) > > 2018-03-20 17:15 GMT+01:00 Bear Giles <[email protected]>: > >> BTW the other database we're supporting is Cassandra. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "jOOQ User Group" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jooq-user/qa8VMSIscAc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
