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
f43bebc7
Commit
f43bebc7
authored
Feb 12, 2014
by
Steve Müller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add upgrade instructions due to automatic platform version detection
parent
180ea45c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
25 additions
and
0 deletions
+25
-0
UPGRADE.md
UPGRADE.md
+25
-0
No files found.
UPGRADE.md
View file @
f43bebc7
# Upgrade to 2.5
## BC BREAK: Doctrine\DBAL\Connection
The visibility of the property
``$_platform``
in
``Doctrine\DBAL\Connection``
was changed from protected to private. If you have subclassed
``Doctrine\DBAL\Connection``
in your application and accessed
``$_platform``
directly, you have to change the code
portions to use
``getDatabasePlatform()``
instead to retrieve the underlying database
platform.
The reason for this change is the new automatic platform version detection feature,
which lazily evaluates the appropriate platform class to use for the underlying database
server version at runtime.
Please also note, that calling
``getDatabasePlatform()``
now needs to establish a connection
in order to evaluate the appropriate platform class if
``Doctrine\DBAL\Connection``
is not
already connected. Under the following circumstances, it is not possible anymore to retrieve
the platform instance from the connection object without having to do a real connect:
1.
``Doctrine\DBAL\Connection``
was instantiated without the
``platform``
connection parameter.
2.
``Doctrine\DBAL\Connection``
was instantiated without the
``serverVersion``
connection parameter.
3.
The underlying driver is "version aware" and can provide different platform instances
for different versions.
4.
The underlying driver connection is "version aware" and can provide the database server
version without having to query for it.
If one of the above conditions is NOT met, there is no need for
``Doctrine\DBAL\Connection``
to do a connect when calling
``getDatabasePlatform()``
.
## datetime Type uses date_create() as fallback
Before 2.5 the DateTime type always required a specific format, defined in
...
...
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