On Thursday 09 June 2005 7:15 am, Puneet Kishor wrote:
> I've been a reading a lot on the "database locked" problem, but still
> need guidance trying to locate the source of my problem.
>
> environment: DBI/DBD::SQLite (latest versions) with SQLite3 (3.2.1) on
> Mac OS X (10.3.9).
>
> I am trying
> Is there any reason why ROUND doesn't return a double?
Because the IEEE storage format most (all?) computers
use to store floating point numbers is binary based, many
values that can be stored exactly in a base 10 system are
rounded slightly to fit into the binary system. This is
similar to
On Thu, 2005-06-09 at 14:49 -0700, Brown, Dave wrote:
> Are the #line macros really needed? Because on Windows if you try to compile
> SQLite with Assembly, Machine Code, Source Code output files generated at
> the same time ( Properties->C/C++ -> Output Files: Assembler Output =
> Assembly,
I dont know how they were generated, but they are in the source zipfile you
download from the sqlite.org site.
-Dave
-Original Message-
From: Thomas Fjellstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 3:16 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] #line macros
On June 9, 2005 03:49 pm, Brown, Dave wrote:
> Are the #line macros really needed? Because on Windows if you try to
> compile SQLite with Assembly, Machine Code, Source Code output files
> generated at the same time ( Properties->C/C++ -> Output Files: Assembler
> Output = Assembly, Machine Code
Are the #line macros really needed? Because on Windows if you try to compile
SQLite with Assembly, Machine Code, Source Code output files generated at
the same time ( Properties->C/C++ -> Output Files: Assembler Output =
Assembly, Machine Code and Source ) which is the /FAcs flag, the
Clark Christensen wrote:
IOW, something like.
$sql = "update t1 set a = ?";
$string = $dbh->quote( qq(some long string; has many
'single quotes') );
$sth = $dbh->prepare($sql);
$rc = $sth->execute($string);
will probably eliminate both the prepare() error, and an
UPDATE error later.
-Clark
--- Puneet Kishor <[EMAIL PROTECTED]> wrote:
> While I await some insight into my previously posted
> "database locking"
> problem, I have a question regarding quoting text.
>
> Does SQLite have any issues with anything other than
> single-quotes? For
> example, with colon, or semi-colon?
>
While I await some insight into my previously posted "database locking"
problem, I have a question regarding quoting text.
Does SQLite have any issues with anything other than single-quotes? For
example, with colon, or semi-colon?
For example, I find occasional complaints if I try to
I received results in the wrong order when using ORDER BY on a column
computed with ROUND, and am interested in knowing if anyone has
encountered a similar problem. I have a solution to my problem at the
bottom of this email, but am not sure it should be necessary. I
appreciate all comments.
On Jun 9, 2005, at 9:35 AM, Jay Sprenkle wrote:
I'm not familar with the wrapper you're using, but don't you have a
commit without a matching begin?
The commit is in the "wrapper," not in the SQL. When making a database
connection, I specified to turn AutoCommit to OFF. Hence, I have to
I'm not familar with the wrapper you're using, but don't you have a
commit without a matching begin? Did you establish a lock on the table
before
trying to update? Are you updating a table that you currently are reading from?
As in:
select * from t;
for each result
update t set field = blah;
I've been a reading a lot on the "database locked" problem, but still
need guidance trying to locate the source of my problem.
environment: DBI/DBD::SQLite (latest versions) with SQLite3 (3.2.1) on
Mac OS X (10.3.9).
I am trying to update a table via the web. The UPDATE in question is
the
13 matches
Mail list logo
