-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support class syntax in HQL query #163
Comments
The actual snapshot accepts more multiparty names. Saying that the hsql class extention would be more difficult to implement because the hierarchy could be much deeper. So it would work here by coincidence. Your class package deepness could be handled. So try the actual snapshot. |
Ok thanks, will do when I get some time. |
What is in the current master does not seems to be enough in my case.
gives me
|
Multipart names were developed to accept database object names. Therefore there is a server schema etc. variable. Class hierarchy would be a different concept of names. I will think about it (being at the beach swimming in the ocean😉). Cheers Tobias |
Thanks for taking that into account :) I have a workaround in the meantime don't worry, just wanted to mention the issue in case other have the need. |
hi @wumpz thanks for considering this. Actually it's a bit more important. Thomas mentioned that we have some workaround which is true but this is causing some API of ours to fail and thus forcing our users to use the XWiki APIs in a certain or it'll fail for them. We cannot really control how they use the XWiki APIs (even though we can document it). So it would be very nice if there was a solution :) Maybe we could even help out although we're totally newbies in the jsqlparser code base? |
I will look into this with higher priority. |
Awesome Tobias! thanks a lot |
Thanks so much Tobias! :) So this will be in jsqlparser 1.3 (or maybe in 1.2.1)? |
The change should do it. The problem was to still accept some SqlServer multipart name specials. (database..table). @vmassol always at work ? ;) This will be in JSqlParser 1.3. I think a major version increment is not necessary. Nevertheless I would appreciate some testing at your side. I included multiple tests. Cheers Tobias and thx for using JSqlParser |
Yes we'll build it and test it, thanks! |
Same for you! :) |
@wumpz I've tested it and it works! Thx, now waiting for the release so that I can fix it in XWiki. Good work! |
In HQL you can have things like "select mymodel.name from com.myproject.MyModelClass as mymodel" but jsqlparser throw a "com is not a valid database reference".
The text was updated successfully, but these errors were encountered: