Skip to content
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

Integrate changes into main project #5

Closed
matthiasblaesing opened this issue Sep 21, 2012 · 2 comments
Closed

Integrate changes into main project #5

matthiasblaesing opened this issue Sep 21, 2012 · 2 comments

Comments

@matthiasblaesing
Copy link
Contributor

Hey,

it would be nice if the fixes/additions done for jsqlparser could be merged into one version again. The author of the project on sourceforge.net indicated, that he would be willing to add authors to the project. So it would be nice if you could join that effort.

A good place to discuss possibilities for further development could be this start of a discussion on sourceforce.net:

https://sourceforge.net/projects/jsqlparser/forums/forum/360150/topic/5652953/index/page/1

Greetings

Matthias

@fbecart
Copy link

fbecart commented Oct 19, 2012

Hi Matthias,

I apologize for the late answer. I agree with you, that's a very useful project and it would be nice to keep all the efforts centralized.

Actually, one of the first changes added to the github fork was the use of Maven instead of Ant. I was about to bring this to the sourceforge-hosted original fork, when I found it also brought a major regression in the build due to a bug in javacc-maven-plugin. I also realized how time-consuming reviewing code can be. So I forgot about it.

Since then I stopped putting much effort in the project - one of the reasons being that it's working very smoothly for my needs and I didn't have to make any change in a while.

I'd be interested to know if some other commiters gave you positive answers.

Florent

@matthiasblaesing
Copy link
Contributor Author

Hey Florent,

please see for discussion here: http://sourceforge.net/projects/jsqlparser/forums/forum/360150/topic/5652953

Greetings

Matthias

@wumpz wumpz closed this as completed Jun 8, 2013
wumpz pushed a commit that referenced this issue Jan 20, 2023
* refactor: Merge REPLACE into UPSERT

fixes #1706

* feat: `DROP TEMPORARY TABLE ...`

fixes #1712

* build: PMD compliance

* ci: Merge master

* feat: Configurable backslash `\` escaping

- Enables `\` as escape character in String Literals (beside SQL:2016 compliant `'`)
- Default is OFF (since its not SQL:2016 compliant)
- Activate per Parser Feature
- Fixes #1638
- Fixes #1209
- Fixes #1173
- Fixes #1172
- Fixes #832
- Fixes #827
- Fixes #578

BREAKING-CHANGE: Backslash Escaping needs to be activated explicitly or else Backslash won't work as Escape Character.

* style: Checkstyle

* style: remove dead code

* style: PMD compliance

* style: Checkstyle, unused import

* feat: allow `S_CHAR_LITERAL` to break lines

- fixes #875
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants