On Thursday, January 26, 2017 at 7:26:53 AM UTC-8, [email protected] wrote: > > Hi Jeremy, > > I am from the Logstash team at Elastic. Logstash is an open source data > ingestion tool written in jruby. It uses inputs to consume data from a > source, filters to transform the data and outputs to send data to a > destination (more likely than not Elasticsearch) > > We use the Sequel gem (thanks for the work on this) in our JDBC input. > Users can connect to a database and fetch records from a database for > further processing. > > We have many users with databases that have support in Sequel as standard > but occasionally we have some that don't - MariaDB and Sybase in particular. > > In the case of MariaDB, the MySql support works OOTB but the user can use > the MySql JDBC driver due to restrictive licensing. >
For MariaDB, if it uses a separate JDBC driver, it should be fairly easy to support. JDBC subadapters are usually quite small. > In the case of Sybase, when using jtds (which loads mssql support > implicitly) the user gets an error because a product version function is > called that does not exist in the Sybase version the user has. > I'm open to modifying the jdbc/jtds adapter so that if you set a :db_type=>:sybase option, it will load the sybase support instead of the mssql support. > My questions are: > > - How amenable are you to getting PRs adding specific support ruby for > these cases? > - Given that these will most likely be variations of existing ones, > will there be a ongoing supprt burden that puts you off? > > For these cases, there is not much additional support burden, as I already test on MariaDB and Sybase. Please submit pull requests for these two issues. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
