Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
30b6622e
Commit
30b6622e
authored
17 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Typo fix.
Euler Taveira de Oliveira
parent
fe385795
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+8
-8
8 additions, 8 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+2
-2
2 additions, 2 deletions
doc/src/FAQ/FAQ.html
with
10 additions
and
10 deletions
doc/FAQ
+
8
−
8
View file @
30b6622e
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Thu Sep 27 02:14:24
EDT 2007
Last updated:
Mon Oct 8 23:19:46
EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -840,13 +840,13 @@
4.21) Why are my table and column names not recognized in my query? Why is
capitalization not preserved?
The most common cause of recognized names is the use of
double-quotes
around table or column names during table creation. When
double-quotes
are used, table and column names (called identifiers)
are stored
case-sensitive, meaning you must use double-quotes when
referencing
the names in a query. Some interfaces, like pgAdmin,
automatically
double-quote identifiers during table creation. So, for
identifiers to
be recognized, you must either:
The most common cause of
un
recognized names is the use of
double-quotes
around table or column names during table creation. When
double-quotes
are used, table and column names (called identifiers)
are stored
case-sensitive, meaning you must use double-quotes when
referencing
the names in a query. Some interfaces, like pgAdmin,
automatically
double-quote identifiers during table creation. So, for
identifiers to
be recognized, you must either:
* Avoid double-quoting identifiers when creating tables
* Use only lowercase characters in identifiers
* Double-quote identifiers when referencing them in queries
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
2
−
2
View file @
30b6622e
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Thu Sep 27 02:14:24
EDT 2007
</P>
<P>
Last updated:
Mon Oct 8 23:19:46
EDT 2007
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</A>
)
...
...
@@ -1097,7 +1097,7 @@ length</TD></TR>
<H3
id=
"item4.21"
>
4.21) Why are my table and column names not
recognized in my query? Why is capitalization not preserved?
</H3>
<P>
The most common cause of recognized names is the use of
<P>
The most common cause of
un
recognized names is the use of
double-quotes around table or column names during table creation.
When double-quotes are used, table and column names (called
identifiers) are stored
<a
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment