Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Add a new FAQ entry that attempts to explain the difference between single quotes and double quotes. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
b405f2eeebeb7bb331da5d2783db6248 |
| User & Date: | drh 2009-03-18 15:14:03 |
Context
|
2009-03-19
| ||
| 00:04 | Fix a typo in the limits.html document. (check-in: 6ddbe9cdf0 user: drh tags: trunk) | |
|
2009-03-18
| ||
| 15:14 | Add a new FAQ entry that attempts to explain the difference between single quotes and double quotes. (check-in: b405f2eeeb user: drh tags: trunk) | |
| 14:19 | Fix typos in documentation. This is the fix for ticket [9ed3b9626c9462e11a557621152f3e2d4eead482] (check-in: cfa4627882 user: drh tags: trunk) | |
Changes
Changes to pages/faq.in.
574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 |
compile-time options when building SQLite.
} {
The [omitfeatures | SQLITE_OMIT_...] compile-time options only work
when building from canonically source files. They do <u>not</u> work
when you build from the SQLite [amalgamation] or from the pre-processed
source files.
It is possible to build a special [amalgamation] that will work with
a predetermined set of SQLITE_OMIT_... options. Instructions for doing
so can be found with the [omitfeatures | SQLITE_OMIT_... documentation].
}
# End of questions and answers.
#############
hd_puts {<h2>Frequently Asked Questions</h2>}
hd_puts {<p>See also <a href="http://www.sqlite.org/cvstrac/wiki?p=SqliteWikiFaq">SqliteWikiFaq</a>.</p>}
|
| > > > > > > > > > > > > > > > > |
574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 |
compile-time options when building SQLite.
} {
The [omitfeatures | SQLITE_OMIT_...] compile-time options only work
when building from canonically source files. They do <u>not</u> work
when you build from the SQLite [amalgamation] or from the pre-processed
source files.
<p>It is possible to build a special [amalgamation] that will work with
a predetermined set of SQLITE_OMIT_... options. Instructions for doing
so can be found with the [omitfeatures | SQLITE_OMIT_... documentation].
}
faq {
My WHERE clause expression <tt>column1="column1"</tt> does not work.
It causes every row of the table to be returned, not just the rows
where column1 has the value "column1".
} {
Use single-quotes, not double-quotes, around string literals in SQL.
This is what the SQL standard requires. Your WHERE clause expression
should read: <tt>column1='column2'</tt>
<p>SQL uses double-quotes around identifiers (column or table names) that
contains special characters or which are keywords. So double-quotes are
a way of escaping identifier names. Hence, when you say
<tt>column1="column1"</tt> that is equivalent to
<tt>column1=column1</tt> which is obviously always true.
}
# End of questions and answers.
#############
hd_puts {<h2>Frequently Asked Questions</h2>}
hd_puts {<p>See also <a href="http://www.sqlite.org/cvstrac/wiki?p=SqliteWikiFaq">SqliteWikiFaq</a>.</p>}
|