The first warning is harmless and results from a prior datatype change.
Dan has already fixed that one. The other four appear to be due to an MSVC
compiler bug, since every (i64%int) operation will always yield a value
that can fit in an int, no?
Ok, thank for this comment. Of course, you
Hi all,
thanks for your replies, but unfortunately they did not answer my original question whether these warnings
are harmless and can be ignored or not. These warnings reported by the VS C++ compiler are about
possible loss of data, so it is a situation when a int64 expression result is
Dear all,
when compiling the latest 3.7.16.1 version of SQLite, the VS compiler complains
about some 64 bit portability issues, see below. May these warning be safely
ignored when compiling 64 bit? All warnings refer to the sqlite3.c amalgamation
file. Thanks in advance.
Line 6766
Dear all,
I've just read the 3.7.11 release notes. This version fixes the LEFT JOIN bug
with OR in the WHERE clause introduced in 3.7.10. Since our software is
currently based on 3.7.10 and it is not easy for us to upgrade to 3.7.11, I
just want to be sure about the bug impacts.
1. I have
Dear Simon and Dan,
thanks for your valuable information, which we were looking for.
Kind regards
Alex
__
Od: Simon Slavin
Komu: General Discussion of SQLite Database
Datum: 21.01.2012 12:49
Předmět: Re: [sqlite] Another 3.7.10
Dear all,
we have two short questions regarding the new 3.7.10 SQLite release.
1. We read about the new powersafe overwrite feature in 3.7.10. We would like
to go on (for a while) without this. If we set SQLITE_POWERSAFE_OVERWRITE to 0 in the
amalgamation file, is this the only thing that
Dear all,
we have another question regarding the 3.7.10 version. We have a database with
cca 10 tables. After creating a new database in 3.7.10 and filling each table
with about 10 - 100 data rows, we noticed that the size of the database is 2x -
4x larger compared to 3.7.9 (using exact same
Systems
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Alexandr Němec [a.ne...@atlas.cz]
Sent: Tuesday, December 27, 2011 8:55 AM
To: sqlite-users@sqlite.org
Subject: EXT :[sqlite] 3.7.9 amalgamation file in VS2005
Dear all,
I
Dear all,
I have one question that is not strictly a SQLite question (sorry), but maybe
someone encountered this problem and found the solution. I have upgraded from
an older SQLite release to 3.7.9 and loaded the amalgamation file into a Visual
Studio 2005 project. But the syntax code
Dear all,
just a quick question, I did not find the answer in the various technical
documents. I have two identical tables with a id INTEGER as a primary key,
which means that SELECTions ORDERed BY id are very fast. Now if I do SELECT *
FROM table1 UNION ALL SELECT * FROM table2 ORDER by id,
doesn't allow attachments. Please send us the output
of pragma integrity_check; on the corrupted database file. Also, is
the database used in WAL mode?
Best regards,
Filip Navara
2011/11/14 Alexandr Němec :
Dear all,
we are using SQLite in our projects. We are using the 3.7.7.1 version
compiled
once more.
Alex
__
Od: Richard Hipp
Komu: General Discussion of SQLite Database
Datum: 14.11.2011 14:03
Předmět: Re: [sqlite] 3.7.7.1 database corruption
2011/11/14 Alexandr Němec
Dear Filip,
thanks for your reply. I thought
Thanks again for your answer,
no, no dangerous pragmas, no journal file removing. Our file system is NTFS so
I hope that no stupid things are done by the file system :). In fact, we
changed just two things only in the amalgamation file - we increased
SQLITE_MAX_PAGE_COUNT to 2 000 000 000
Dear all,
we are using SQLite in our projects. We are using the 3.7.7.1 version compiled
on Windows platform from the amalgamation file. One of our servers crashed
badly (power outage) and after the server restarted, we saw that the database
was corrupt (all queries we tried return
14 matches
Mail list logo
