On 2 May 2018, at 5:22pm, dmp wrote:
> Since I'm using Java and JDBC I was retrieving numeric fields in PostgreSQL
> with getString(), handles all, then using Integer.parseInt(stringValue) for
> BigInts in storing to SQLite.
>
> There lies the problem since
> SQLite integers are all 64 bit - I don't about postgress, so unless
> postgress allows integers bigger than 64 bit, and you use them, you should
> be OK with your table definitions above.
> Paul
Hello,
That really provides insight to the real issue, I was having and so therefore
the question.
Ad 2) Yes, this is expected. SQLite uses file locking to implement transactions.
Ad 1) Using WAL mode, readers can read data as it was before the write
transaction started.
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von
HI every one
i use sqlite3 3.22.0 verison on embeded arm9 system
when i insert a lot of data like this
begin_transaction
sqlite3_prepare_v2();
for(i = 0;i<2040;i++)
{
sqlite3_bind_text();
sqlite3_bind_blob();
sqlite3_step();
sqlite3_reset();
sqlite3_clear_bindings();
}
Thank you so much. I'm always impressed by the responsiveness of the SQLite
team. Very grateful for your help and hard work.
On Wed, May 2, 2018 at 3:13 AM, Dan Kennedy wrote:
> On 05/02/2018 03:50 AM, Charles Leifer wrote:
>
>> Hi all,
>>
>> I'm noticing a bug in the
On 05/02/2018 03:50 AM, Charles Leifer wrote:
Hi all,
I'm noticing a bug in the transitive closure extension in the latest
version of SQLite.
Thanks for reporting this. Should now be fixed here:
http://www.sqlite.org/src/info/0c67150749cb3d06
Dan.
Reproducing requires the closure
Counterexample:
List of Tuples: (1,1), (1,3),(3,1),(3,3),(2,2) with nX = nY = 2
(2,2) is within the "square" but needs to be removed
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Barry Smith
Gesendet: Mittwoch, 02. Mai
7 matches
Mail list logo