The concepts I like the best so far are "in-process" or "integrated" or
something library-themed. -- Darren Duncan
On 2020-01-27 2:18 p.m., Richard Hipp wrote:
For many years I have described SQLite as being "serverless", as a way
to distinguish it from the
eans?
My first thought on reading that was that "mounting" meant using the ATTACH
command, since in the analogy of the SQL environment as a filesystem, using
ATTACH is like mounting a volume within the filesystem in order to access the
volume's contents, which are tabl
Generally speaking, you want to support union types.
Do you have any questions to help you understand this?
-- Darren Duncan
On 2019-12-13 2:49 p.m., František Kučera wrote:
I know that SQLite uses dynamic types, so it is not easy… But what is the best
way to determine the column type of a result set
On 2019-10-30 12:52 p.m., Keith Medcalf wrote:
On Wednesday, 30 October, 2019 13:23, Darren Duncan
wrote:
On 2019-10-30 12:02 p.m., Simon Slavin wrote:
On 30 Oct 2019, at 6:56pm, Darren Duncan wrote:
"Generated columns may not be used as part of the PRIMARY KEY. (Future
ver
On 2019-10-30 12:02 p.m., Simon Slavin wrote:
On 30 Oct 2019, at 6:56pm, Darren Duncan wrote:
"Generated columns may not be used as part of the PRIMARY KEY. (Future versions of
SQLite might relax this constraint for STORED columns.)"
Replace with this:
"VIRTUAL genera
On 2019-10-30 3:12 a.m., Richard Hipp wrote:
On 10/30/19, Darren Duncan wrote:
Ideally a PRIMARY KEY would have no restrictions that a UNIQUE constraint
lacks;
they are conceptually the same thing, a subset of the columns of the row
that
uniquely identifies the row in the table
.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
identifies the row in the table, and designating one as PRIMARY is
completely arbitrary in that sense.
The benefits I ascribed to generated columns as a foundation would be greatly
weakened if a PRIMARY KEY can't use them.
Thank you.
-- Darren Duncan
, and omitting those is quite reasonable.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
integer be able to represent all the
subsecond time precision people would want? -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Forms, eg NFD vs
NFC, and its not about codepoint encodings like UTF-8 vs UTF-16 etc. -- Darren
Duncan
On 2019-10-20 8:03 p.m., Rowan Worth wrote:
On Sun, 20 Oct 2019 at 17:04, Simon Slavin wrote:
Another common request is full support for Unicode (searching, sorting,
length()). But even
n embedded library, in contrast to being a server with multiple
concurrent users.
What are the main missing "essential basics of the SQL standards" that you think
can be added without compromising the "liteness"?
-- Darren Duncan
__
a lot of confusion. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
.
-- Darren Duncan
On 2019-07-12 7:19 a.m., Charles Leifer wrote:
I ran into a somewhat surprising result and wanted to just get a little
clarification.
I'll use the following statement as an example:
SELECT SUBSTR(?, 1, 3) == ?
And the parameters will be:
* "abcde"
* "abc&q
for this is, since that page doesn't seem to say. Why
there are any restrictions at all of this nature in triggers. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman
to those that don't. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
If you look at the release history, major SQLite releases come out every 2-3
months on average, and over the last year they weren't more than 3 months apart.
So by that pattern, 3.27 will probably come out not more than a month from
now. -- Darren Duncan
On 2019-01-24 3:55 PM, Jens Alfke
On 2018-12-17 9:16 AM, James K. Lowden wrote:
On Sat, 15 Dec 2018 01:24:18 -0800
Darren Duncan wrote:
If yours is a financial application then you should be using exact
numeric types only
Color me skeptical. That very much depends on the application. IEEE
double-precision floating point
capable of representing the largest integers
you could ever possibly need to use for storage or intermediate calculations, if
necessary a variable size representation such as BigInt or binary-coded-decimal.
-- Darren Duncan
___
sqlite-users mailing list
On 2018-12-15 2:15 AM, Frank Millman wrote:
On 2018-12-14 11:24 AM, Darren Duncan wrote:
If yours is a financial application then you should be using exact numeric types
only, such as integers that represent multiples of whatever quantum you are
using, such as cents; fractional numbers
If yours is a financial application then you should be using exact numeric types
only, such as integers that represent multiples of whatever quantum you are
using, such as cents; fractional numbers are a display or user input format
only, and in those cases they are character strings. -- Darren
I find it strange that there's a big global lock problem with APFS considering
one of the biggest design and selling points was that APFS did NOT use global
locks like the old HFS+ did. -- Darren Duncan
On 2018-10-29 7:13 PM, Simon Slavin wrote:
This post is about a problem with Apple's new
instances of Fossil. --
Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
password everywhere that uses passwords, and one presumably already
has dozens or more of those, so if they use a password manager, the SQLite forum
is just another one it automatically handles. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users
a copy back in your email, so its like you wrote it with email.)
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
else. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
he DBMS can use whatever order it feels like at any time without any prior
notice of changes. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 2018-08-24 11:58 PM, Thomas Kurz wrote:
What is the value of a built-in UNSIGNED type when we already have INTEGER? I
can't think of any. -- Darren Duncan
Signed integers only allow half the range of values of unsigned ones. You
cannot store a pointer value in them. (You can by casting
On 2018-08-20 11:46 PM, D Burgess wrote:
Is there a historical reason why sqlite does not have a UNSIGNED type
to go with INTEGER?
What is the value of a built-in UNSIGNED type when we already have INTEGER? I
can't think of any. -- Darren Duncan
se one with an email interface so that
one can choose to receive an email for each forum message (it doesn't have to
support posting via email though), and download archives of messages, so we
don't go backwards. -- Darren Duncan
___
sqlite-users mailing list
it. Also serves as a good "default" name, like the good default character
string value would be empty or the good default number value would be zero.
I also believe that database tables with zero columns should be allowed, but
that's a separate matter.
-- Darren Duncan
On 2017-10-
hat if the column list is constant (the INTO is written
normally) then the VALUES clause should be replaceable with an array-valued
parameter, and no recompile should be needed because what specific fields to
expect is known when parsing the SQL. -- Darren Duncan
__
a
VALUES clause or whatever can go in the second argument for an IN.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
I agree that being able to bind Array values is very useful, but this shouldn't
need any new syntax in the SQL, the same ? should be acceptable; this shouldn't
be any different than the distinction between binding a number vs text etc. --
Darren Duncan
On 2017-09-15 11:40 PM, Wout Mertens
message. Also, the spam messages used and replied to
messages sent only minutes before. There could be a question of whether the
mailing list validates that the sender of a message actually is the sender, or
whether they let them in just because they say they are someone on the list. --
Darren
ar
inputs or not, so that would be an added complexity.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
MySQL does, and that's just for SQL DBMSs.
Is it worth having some kind of official statement from the makers of SQLite
about this, that MySQL is using false advertising?
Or is the idea that SQLite has the most installations not easily provable?
-- Dar
nsubscribe
yourself.
-- Darren Duncan
On 2017-06-17 5:54 PM, Mike Henry wrote:
or tell me how to remove myself
On Sat Jun 17 2017 14:04:02 GMT-0500 (Eastern Standard Time), Mike Henry
<mhenryd...@yahoo.com> wrote:
thanks
___
sqlite-users mai
Unless I misunderstand the desired result, this query would be better formulated
using 2 left joins instead, like this:
SELECT ...
FROM Persons LEFT JOIN Pets ... LEFT JOIN PetAccessories ...
-- Darren Duncan
On 2017-03-22 2:22 AM, Chris Locke wrote:
An interesting discussion
either.
-- Darren Duncan
On 2017-03-21 8:42 AM, Daniel Kamil Kozar wrote:
Seeing how SQLite was created in 2000, it seems like nobody really
needed this feature for the last 17 years enough in order to actually
implement it.
Last I heard, patches are welcome on this mailing list. Don't keep us w
On 2017-02-14 5:05 PM, Darren Duncan wrote:
On 2017-02-14 4:46 PM, Richard Hipp wrote:
This is yet another reason why I say "threads are evil". For
whatever reason, programmers today think that "goto" and pointers and
assert() are the causes of all errors, but threads ar
if you are
explicitly using "threads" in code.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
laring the operation
associative and commutative and lacking of side-effects or whatever. -- Darren
Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
erent name.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
other
possible value you could store in the MySQL you can now store in SQLite,
consistently.
-- Darren Duncan
On 2016-12-01 12:08 AM, Werner Kleiner wrote:
As I can see storing prices is a topic with different ways and
different solutions.
The advice to store prices in Cent or Integer:
Yes you
On 2016-11-30 3:14 PM, Keith Medcalf wrote:
On Wednesday, 30 November, 2016 17:58, Darren Duncan <dar...@darrenduncan.net>
said:
On 2016-11-30 2:43 PM, Keith Medcalf wrote:
You were given a good recommendation save everything in "cents". Which
might also be a good so
ent values
than the exact amount you insert or withdraw, do you? -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
already occurred then. I personally think the subject has
already run its course. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
You didn't say if the other tasks need write access to the database or if it is
just read-only. If the others only need read-only, let them access a copy of
the database while you make your changes in another copy, then just swap the
databases when done. -- Darren Duncan
On 2016-10-15 1:21
for that. -- Darren Duncan
On 2016-10-08 12:31 AM, Darren Duncan wrote:
So, if you don't want to pay the one-time fee for the SQLite Encryption
Extension et al to get database-level security, your only option really is to
encrypt individual fields at the application level that you want to protect
for that, the specific
options depending on your choice of programming language. But using those has
nothing to do with SQLite specifically, so your answer wouldn't be found on this
SQLite forum, but rather forums for your programming language. -- Darren Duncan
On 2016-10-08 12:18 AM, Damien Sykes
application and you don't want people on the open internet
from accessing the database, fair enough, but that's an application-level
solution; what you're asking for here is that people who have direct access to
the SQLite database file are blocked by a password, and this I question.
-- Darren
single-element row while "(42)" is simply the value 42 since parens are also
used for forcing evaluation precedence of expressions.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.
You can also access that value within your Perl code, in a DBMS-agnostic
fashion, with the appropriate DBI routine:
http://search.cpan.org/dist/DBI/DBI.pm#last_insert_id
-- Darren Duncan
On 2016-09-11 2:59 PM, mikeegg1 wrote:
I forgot I could use it inside the shell. Thanks.
On Sep 11
as with my computer at its default size while loading.
Site still seems navigatable. I didn't go very far though. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
. Anyone can do anything about it?
As was in the news a month back, Gmane shut down its web interface.
Hopefully every list that relied on it also has other archives.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http
On 2016-08-04 7:27 AM, Jim Callahan wrote:
Steps
Agree with Darren Duncan and Dr. Hipp you may want to have at least 3
separate steps
(each step should be a separate transaction):
1. Simple load
2. Create additional column
3. Create index
Have you pre-defined the table you are loading data
it successful. Or otherwise at some point
you should see the smallest point where the hang occurs. -- Darren Duncan
On 2016-08-03 8:00 PM, Kevin O'Gorman wrote:
I'm working on a hobby project, but the data has gotten a bit out of hand.
I thought I'd put it in a real database rather than flat
er conform with the
standard. Could you include an item in the release notes about this? That
would be a useful thing to draw the attention of actual or potential users in
stricter environments where it matters.
-- Darren Duncan
___
sqlite-users mailing list
sq
nd how best to document the change.
Thoughts on that proposal?
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
, hence I say use Double everywhere.
-- Darren Duncan
On 2016-07-05 4:34 PM, Ertan Küçükoğlu wrote:
Hardware that the application will run is ~1Ghz Atom CPU, ~1GB RAM, regular Laptop HDD
(no SSD). Time to time, there will be calculations, Network file transfer, and DLL
function calls (all three
y time is just going to cause you trouble.
And really, are you sure using Single would actually help performance? Have you
measured it in a real workload? More likely on modern devices it won't be any
faster and you will have lost your accuracy for nothing
.
Ertan Küçükoğlu
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
then older SQLite versions will still work with it.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ng the row, and that way, you don't
need to ask afterwards what the id is, you already know because it is the value
you told it to use when doing the insert. -- Darren Duncan
On 2016-06-27 11:58 PM, Hick Gunter wrote:
Do not use SQLite for concurrent access over a network connection. Locking
is within a month or so of the first time
I ever released open-source code to the public (on CPAN).
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 2016-05-28 12:49 PM, r.a.n...@gmail.com wrote:
@Daren
Any reasons for the thumbs down on MySQL? Their workbench is better that Toad
...
On May 27, 2016, at 10:00 PM, Darren Duncan <dar...@darrenduncan.net> wrote:
On 2016-05-27 2:28 PM, Balaji Ramanathan wrote:
But when I was de
On 2016-05-27 2:34 AM, Tim Streater wrote:
On 27 May 2016 at 08:56, Darren Duncan <dar...@darrenduncan.net> wrote:
On 2016-05-26 9:00 PM, Balaji Ramanathan wrote:
The main advantage of forums, and I follow a bunch of them, is that I choose
when I want to stop my regular d
for anything. If you want
something bigger than SQLite, look at Postgres instead of MySQL. As a bonus,
the Postgres documentation is much better. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http
, rather that's an argument for not using
your work email to subscribe to non-work discussion lists; use a non-work email
for the discussion lists instead. You can also configure your email client to
only check email when you tell it to rather than constantly. -- Darren Duncan
zation. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
r example of list plus/sum which is repetition of the dyadic
"x
+ y". List MIN is NOT a repeated application of "x less than y". -- Darren
Duncan
terminate.
The options with point 1 are not only deterministic but fully relational.
-- Darren Duncan
INCT
> and GROUP BY, the query parser should require that every column in the
> column list should appear in the ORDER BY list. If it does not, then the
> result is indeterminate.
>
> Sqlite already permits indeterminate queries, but other SQL engines do not.
Not EVERY column, just a superkey of the result columns should suffice.
-- Darren Duncan
On 2016-05-15 10:50 PM, J Decker wrote:
> On Sun, May 15, 2016 at 10:02 PM, Darren Duncan
> wrote:
>> On 2016-05-15 9:56 PM, J Decker wrote:
>>>
>>> On Sun, May 15, 2016 at 9:29 PM, Darren Duncan
>>> wrote:
>>>>
>>>> O
On 2016-05-15 9:56 PM, J Decker wrote:
> On Sun, May 15, 2016 at 9:29 PM, Darren Duncan
> wrote:
>> On 2016-05-15 12:35 AM, Simon Slavin wrote:
>>>
>>> All true. But it brings up a question. Suppose the following:
>>>
>>> first second
>&g
On 2016-05-15 12:35 AM, Simon Slavin wrote:
> On 15 May 2016, at 6:04am, Darren Duncan wrote:
>
>> You seem to be forgetting the fact that LIMIT/OFFSET is not its own clause,
>> rather it is an extension to the ORDER BY clause and only has meaning within
>>
itself (no offset) could be
standalone, but then without an ORDER BY all say "LIMIT N" means is "give me a
random subset of size N of the rows", but then there probably is alternate
syntax that may say this more explicitly, eg "PICK N".
-- Darren Duncan
erroneous title
"SQL:20nn Working Draft Documents".
The actual PDF files are datestamped 2011 Dec 22.
Unless you need something 100% perfect, those are for all intents and purposes
the same as the official standard.
I've relied on the up to date texts of that website for the last 15 year
t would fail. Having an if-then
version is more reliable in general. Also less ambiguous as ROUND doesn't
behave the same everywhere. -- Darren Duncan
On 2016-05-09 7:54 PM, Rowan Worth wrote:
> On 10 May 2016 at 08:31, Darren Duncan wrote:
>
>> The Ceiling function is not that simple, unless you know that your rank
>> and outOf are always non-negative numbers. If they might be negative, you
>> would -1 rather
way?
The Ceiling function is not that simple, unless you know that your rank and
outOf are always non-negative numbers. If they might be negative, you would -1
rather than +1 when the result is negative. -- Darren Duncan
gt; SQLite?
As far as I know the vast majority of servers on the internet are Linux, and
while this is less than the number of phones, I would hardly call their
absolute
numbers a rounding error. -- Darren Duncan
then be metadata without having
to be a unique identifier. This way you don't confuse 2 files with the same
name but different content or vice-versa, and you gain other benefits. --
Darren
Duncan
On 2016-04-28 3:43 PM, R Smith wrote:
> On 2016/04/28 8:27 PM, deltagamma1 at gmx.net wrote:
>
rformance benefit
to explicitly declaring fields with a maximum length. This also fits in with a
proper clean data model, where you just declare details significant to the
business model and not to dictate how resources are managed. You should only
declare a length if that is actually significant to the validity of the data,
and then its functionally just like a CHECK constraint. -- Darren Duncan
y see a database where the
numbers
don't add up properly, as if it were corrupt; that is what "inconsistent"
means.
-- Darren Duncan
most are inapplicable in
any
given case, eg some only apply to strings, some only to numbers, etc. And so,
just expressing the type definition as a SQL fragment like table_info()
currently does provides a compact generic representation with all the details,
same as in CREATE TABLE. -- Darren
On 2016-04-06 6:00 AM, Cezary H. Noweta wrote:
> On 2016-04-06 09:43, Darren Duncan wrote:
>> On 2016-04-05 10:19 AM, Richard Hipp wrote:
>
>>> It seems to me that the most consistent answer is that the "type" of
>>> columns in a VIEW should always be an e
the returned column type is the empty string.
Personally, I think using the expression value type is the best though, and
works without any schema changes.
-- Darren Duncan
hing for you to keep between
> "pages"; you just start from where you stopped.
>
> How exactly is the first way "easiest"?
>
> --jkl
If these are pages displayed to the user, they may want to scroll backwards at
some point; I don't expect that sqlite3_step is bidirectional, but if it is
that's a pleasant surprise; the approaches using SQL can go backwards as easily
as forwards, but really it depends on the use case. -- Darren Duncan
se WHERE and LIMIT as Clemens suggested in all cases I
> know of.
>
>
> Cheers,
> Ryan
Ryan, I think I was the one who actually previously said most of this stuff you
are talking about, rather than Clemens, including about using WHERE and LIMIT
and about consequences of OFFSET skipping or repeating lines due to other
users'
updates. -- Darren Duncan
Using OFFSET means you have to sort and count all the records you're skipping
before getting to the ones you want, and using WHERE means you can avoid
counting and only sort the ones you're not skipping. That is how it is,
regardless of what that document you saw says. -- Darren Duncan
in order to simplify things, then you live with
the
limitations and sluggishness of LIMIT and OFFSET, as those limitations are
systemic to LIMIT and OFFSET.
-- Darren Duncan
> At 2016-03-03 10:42:37, "Darren Duncan" wrote:
>> On 2016-03-02 5:02 AM, ?? wrote:
>>>
tc the field
values
for that last row.
So you're sure to get the rows just after the ones you just saw, and later
pages
shouldn't be any slower than earlier ones.
This approach is also resilient to arbitrary changes to the database between
page views so you don't either repeat rows or skip rows
David, unless you're wanting to use SQLite's built-in datetime operators, then
just encode yours somehow and put them in another field type, and decode them
on
retrieval into your own datetime types. Depending what you encode them as,
pick
the appropriate built-in type. -- Darren Duncan
Okay, I think this clears some things up.
On 2016-01-08 11:36 AM, Warren Young wrote:
> On Jan 8, 2016, at 12:39 AM, Darren Duncan wrote:
>>
>> I interpreted your request as if current systems' error outputs at execute
>> time were printing out the problematic SQL state
ite with all applications regardless of whether it is
used or not.
Apples and oranges.
-- Darren Duncan
or dependence on some system
SQLite library, but Perl itself doesn't have this built-in nor should it.
In the Perl 4 days you had to recompile Perl to make a version that can talk to
a DBMS, eg "Oraperl", but thankfully with Perl 5 (1994 or so) we did away with
that.
-- Darren Duncan
On 2016-
.
-- Darren Duncan
On 2016-01-07 5:55 PM, Warren Young wrote:
> On Jan 7, 2016, at 6:04 PM, Darren Duncan wrote:
>>
>> On 2016-01-07 4:55 PM, Warren Young wrote:
>>> 2. There is no ?preview? mechanism.
>>
>> The current method of binding is correct. All we really need
problems due to syntax errors, those presumably would be caught at prepare time
or have nothing to do with the execute time values anyway as syntax errors are
by definition a SQL syntax problem. -- Darren Duncan
1 - 100 of 571 matches
Mail list logo
