Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
62d45261
Commit
62d45261
authored
Jun 15, 2002
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Ooops, fix busted markup.
parent
32fecad8
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/src/sgml/syntax.sgml
doc/src/sgml/syntax.sgml
+3
-3
No files found.
doc/src/sgml/syntax.sgml
View file @
62d45261
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.6
2 2002/06/15 21:28:55
tgl Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.6
3 2002/06/15 22:15:03
tgl Exp $
-->
-->
<chapter id="sql-syntax">
<chapter id="sql-syntax">
...
@@ -1471,11 +1471,11 @@ SELECT somefunc() OR true;
...
@@ -1471,11 +1471,11 @@ SELECT somefunc() OR true;
be used. For example, this is an untrustworthy way of trying to
be used. For example, this is an untrustworthy way of trying to
avoid division by zero in a WHERE clause:
avoid division by zero in a WHERE clause:
<programlisting>
<programlisting>
SELECT ... WHERE x
<> 0 AND y/x >
1.5;
SELECT ... WHERE x
<> 0 AND y/x >
1.5;
</programlisting>
</programlisting>
but this is safe:
but this is safe:
<programlisting>
<programlisting>
SELECT ... WHERE CASE WHEN x
<> 0 THEN y/x >
1.5 ELSE false END;
SELECT ... WHERE CASE WHEN x
<> 0 THEN y/x >
1.5 ELSE false END;
</programlisting>
</programlisting>
A CASE construct used in this fashion will defeat optimization attempts,
A CASE construct used in this fashion will defeat optimization attempts,
so it should only be done when necessary.
so it should only be done when necessary.
...
...
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