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
fc913a3d
Commit
fc913a3d
authored
Sep 16, 2006
by
zYne
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added some line breaks
parent
75242e50
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
5 deletions
+9
-5
Getting started - Setting table definition - Field(Column) naming.php
...ted - Setting table definition - Field(Column) naming.php
+7
-4
documentation.php
manual/documentation.php
+2
-1
No files found.
manual/docs/Getting started - Setting table definition - Field(Column) naming.php
View file @
fc913a3d
One
problem
with
database
compatibility
is
that
many
databases
differ
in
their
behaviour
of
how
the
result
set
of
a
query
is
returned
.
MySql
leaves
the
field
names
unchanged
,
which
means
if
you
issue
a
query
of
the
form
"SELECT myField FROM ..."
then
the
result
set
will
contain
the
field
'myField'
.
Unfortunately
,
this
is
just
the
way
MySql
and
some
other
databases
do
it
.
Postgres
for
example
returns
all
field
names
in
lowercase
"SELECT myField FROM ..."
then
the
result
set
will
contain
the
field
'myField'
.
<
br
/>
<
br
/>
Unfortunately
,
this
is
just
the
way
MySql
and
some
other
databases
do
it
.
Postgres
for
example
returns
all
field
names
in
lowercase
whilst
Oracle
returns
all
field
names
in
uppercase
.
"So what? In what way does this influence me when using Doctrine?"
,
you
may
ask
.
Fortunately
,
you
don
't have to bother about that issue at all. Doctrine takes care of this problem
you
may
ask
.
Fortunately
,
you
don
't have to bother about that issue at all. <br />
<br />Doctrine takes care of this problem
transparently. That means if you define a derived Record class and define a field called '
myField
' you will always
access it through $record->myField (or $record['
myField
'], whatever you prefer) no matter whether you'
re
using
MySql
or
Postgres
or
Oracle
ect
.<
br
/>
...
...
manual/documentation.php
View file @
fc913a3d
...
...
@@ -94,11 +94,12 @@ $menu = array("Getting started" =>
"Starting new project"
,
"Setting table definition"
=>
array
(
"Introduction"
,
"Field(Column) naming"
,
"Data types and lengths"
,
"Constraints and validators"
,
"Default values"
,
"Enum emulation"
,
"Field(Column) naming"
),
"Record identifiers"
=>
array
(
"Introduction"
,
...
...
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