Your changes has been incorporated into v3 branch #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd showing methods, have query replace, should solve issue with postgres
…o primary id field will throw error
…lved and not set in an set sequence
…ses with it currently
… in vendor class driver for all values passed
… statements change on entering Query method call
…ndling, test each and correct call handling
…dors prepare functions for arguments variables supplied, testing on ms sql server
…tParamaters functions, added query_prepared for mysql, sqlite3 and pdo These functions will allow supplied variables, values, string or array, to be auto converted to placeholders then bind and executed, returning an result set.
…ng function for xss protection
…etup basic escape function template use if none available by sql vendor
sjstoelting
approved these changes
May 22, 2018
|
Hi @techno-express Thanks for you work merging my stuff into ezSQL back again. Stefanie |
|
Thanks, I forgot to let you know of master branch is v3 now. That's goods
others still asking about the project. I thought i was the only one too see
the real benefit, and ease of use it brings.
I'm working on v4, will be awhile, but will be breaking changes, and more
interoperable with PSR-2, PSR-4, PSR--11 compliance. The project not going
dead on my watch.
…On Thu, Oct 11, 2018 at 10:02 AM Stefanie Janine Stölting < ***@***.***> wrote:
Hi @techno-express <https://github.com/techno-express>
I merged the ezSQL master branch from upstream and switched the default
branch to master.
In my branch ezSQL-3.0 I've added the information to use the original
sources of ezSQL. In addition I published that as news on my website, I've
seen several page accesses to my ezSQL news list.
Thanks for you work merging my stuff into ezSQL back again.
Stefanie
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AcZ6lV2YoySIhg1Qj0wIErWRFHgqnNbkks5uj096gaJpZM4S5Yun>
.
--
Sincerely,
Lawrence Stubbs
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Hi,
Just to let you know, i have forked and added onto most of your work on ezSQL. It has now been added into an branch and eventually will be part of the main repo.
I am one of the collaborators to the project now. I was in the process of write my own unit tests and other major rewrites, then i came upon your pull request, seen it closed with no reasons. A lot of great changes too.