Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
D
doctrine-dbal
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Tomáš Trávníček
doctrine-dbal
Commits
dfe0bd85
Commit
dfe0bd85
authored
Oct 27, 2011
by
Andreas Fischer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
'clearly separated' instead of 'separated clearly'.
parent
8643b242
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
data-retrieval-and-manipulation.rst
en/reference/data-retrieval-and-manipulation.rst
+1
-1
No files found.
en/reference/data-retrieval-and-manipulation.rst
View file @
dfe0bd85
...
...
@@ -77,7 +77,7 @@ every value passed into the query using ``mysql_real_escape_string()`` to avoid
If you start adding more and more parameters to a query (for example in UPDATE or INSERT statements)
this approach might lead to complex to maintain SQL queries. The reason is simple, the actual
SQL query is not
separated clearly
from the input parameters. Prepared statements separate
SQL query is not
clearly separated
from the input parameters. Prepared statements separate
these two concepts by requiring the developer to add **placeholders** to the SQL query (prepare) which
are then replaced by their actual values in a second step (execute).
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment