-
Notifications
You must be signed in to change notification settings - Fork 158
sql or no-sql output #15
Comments
Hey @mojtabye. I had a similar question in November: I think a plugin system for formatting output here would be useful. However, I wouldn't want to duplicate work if it isn't necessary - i'll have to look and see what my options are here. On that same note, I'd like to get a 1.0 version out this year, and that probably means looking pretty closely at the default output of the component. I wonder if it would useful to try to emulate the jQuery QueryBuilder output, since that looks pretty popular? And it could pair with their server-side libraries. Final note: I am hesitant about adding a SQL output option, b/c I don't want to encourage folks to generate SQL on the front-end and then use it server-side. I get why it would be useful, though. |
i would be interested in sql option and also how to integrate with asp |
I did something similar at backend with java. |
I don't think the front-end should output sql but a package for the back-end to parse the front-end output into sql would be great. |
Note to self - had an inquiry about an output option for Lucene queries. |
Is there a Laravel/Eloquent rest endpoint implementation out there? if not, someone interested in creating one with me? SQL Output update |
@dabernathy89 I really like your idea of a plugin system, so I could use SQL or Lucene output and allow others to enhance modify or work on it without impact. |
I'd like to second the use case of generating SQL entries. in our case, we are using a widget to generate a SQL command, but not to execute it, which is then saved as an entry into a query list that is fed to the backend configuration. so it's an internal tool, not a direct database query, which would not have the pitfalls of it. If anyone know how I can take the object generated by this component and create an SQL query please let me know, maybe some other package? |
http://querybuilder.js.org has the ability to convert the output to mongo or SQL queries, do you have any plan to add this future?
The text was updated successfully, but these errors were encountered: