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

Update SqliteParser.php #203

Merged
merged 1 commit into from
Feb 27, 2022
Merged

Update SqliteParser.php #203

merged 1 commit into from
Feb 27, 2022

Conversation

r4ndsen
Copy link

@r4ndsen r4ndsen commented Dec 9, 2021

as describes here: #183

in sqlite a columnname containing : is valid, however the sqlite queryparser currently does not support this.

adjusting the $skip and $split fixed it for us

in sqlite a columnname containing `:` is valid, however the sqlite queryparser currently does not support this.

adjusting the `$skip` and `$split` fixed it for us
@harikt
Copy link
Member

harikt commented Jan 28, 2022

We need a test so there will be no regression. Is it possible?

@harikt
Copy link
Member

harikt commented Feb 19, 2022

Hi @r4ndsen,

Do you want this go to 3.x only or 4.x and 5.x as well ? Also if possible write a test case.

@harikt harikt mentioned this pull request Feb 26, 2022
@harikt
Copy link
Member

harikt commented Feb 26, 2022

I have added a test. @koriym I guess we can merge this feature.

And may be release 3.x soon.

@harikt harikt merged commit 90aa74c into auraphp:3.x Feb 27, 2022
@harikt harikt mentioned this pull request Feb 28, 2022
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

Successfully merging this pull request may close these issues.

2 participants