Re: [sqlite] fixing time-warp

On Wed, Nov 5, 2014 at 7:07 AM, E. Timothy Uy wrote: > The problem is ultimately not time-warps. DRH can confirm - the problem is > actually inside fossil and sqlite.fossil. Very early on in sqlite.fossil > there are entries in the plink table where the parent id (pid) is greater

[sqlite] ANN: SQLite PHP Generator 14.10 released

Hi! SQL Maestro Group announces the release of SQLite PHP Generator 14.10, a powerful GUI frontend for Windows that allows you to generate feature-rich CRUD web applications for your SQLite database. http://www.sqlmaestro.com/products/sqlite/phpgenerator/ Online demo:

Re: [sqlite] fixing time-warp

As I walked away to do the dishes, these verses from Matthew suddenly came to mind: The LORD said unto my Lord, Sit thou on my right hand, till I make thine > enemies thy footstool? If David then call him Lord, how is he his son? I think I'll just be quiet now. Blessings, Tim On Tue, Nov 4,

Re: [sqlite] fixing time-warp

I am not behind http://repo.or.cz/w/sqlite.git - though Kyle (the one behind it) has some good ideas that would be nice to get into fossil. But he doesn't care to try to get them into fossil. I do. Please don't misinterpret the answers below as any kind of disrespect for DRH, SQLite or fossil -

Re: [sqlite] fixing time-warp

Maybe E. Timothy Uy is the person behind http://repo.or.cz/w/sqlite.git ? On Tue, Nov 4, 2014 at 7:15 PM, Warren Young wrote: > On Nov 3, 2014, at 7:01 PM, E. Timothy Uy wrote: > > > Is that a philosophical question? :) > > No, it’s a persuasion challenge. >

Re: [sqlite] x64 vs x32 DLL

On Nov 4, 2014, at 5:25 PM, Keith Medcalf wrote: > Assuming that you do rebuild the entire application as 64-bit, it will > consume at least twice the amount of memory as the x86 version and run slower > in user code. [citation needed] On 32-bit Cygwin: $ ls -lh `which

Re: [sqlite] x64 vs x32 DLL

On Tuesday, 4 November, 2014 12:35, jose isaias cabrera asked: >I have an application that is written for x32 machines. However, we now >have a few machines that are x64 and all is well when we are using the >precompiled x32 DLLs provided by

Re: [sqlite] fixing time-warp

On Nov 3, 2014, at 7:01 PM, E. Timothy Uy wrote: > Is that a philosophical question? :) No, it’s a persuasion challenge. I’ll propose it in two parts: 1. Why is it a good idea for you, E. Timothy Uy, to dump the SQLite code repo into a Git repo? What does this achieve, that

Re: [sqlite] How to check if a record exists

On Tue, 4 Nov 2014 21:47:20 + "Drago, William @ CSG - NARDAEAST" wrote: > I've been pulling my hair out trying to figure how to use EXISTS. I have several examples at http://www.schemamania.org/sql/#missing.table. > Is there a better/recommended way in SQLite to

Re: [sqlite] How to check if a record exists

On 11/4/2014 4:47 PM, Drago, William @ CSG - NARDAEAST wrote: "SELECT count(1) DatasetID FROM UUT_Info where DatasetID = " + id + ";"; You could do select exists (select 1 from UUT_Info where DatasetID = :id); This returns 0 or 1 (record absent/present). May work

Re: [sqlite] x64 vs x32 DLL

On Tue, 04 Nov 2014 22:20:23 +0200 RSmith wrote: > The best way to think of the 64 bit upgrade in normal programming is: > "Able to do larger accuracy calculations at more or less the same > speed". Eh, more accurate how? Every 32-architecture I compiled for supported

Re: [sqlite] How to check if a record exists

If all you want to know is whether a record matching a particular field value exists, then what you did is appropriate. The EXISTS construct is generally for filtering one table with another. That being said, you should be using bind parameters rather than stitching id into the SQL string

[sqlite] How to check if a record exists

All, I've been pulling my hair out trying to figure how to use EXISTS. I've had no luck with it (syntax errors) and I've resorted to this. Is there a better/recommended way in SQLite to check if a record exists? static bool IDisDuplicate(string dbFileName, int id) { int

Re: [sqlite] x64 vs x32 DLL

> > On 2014/11/04 21:34, jose isaias cabrera wrote: >> Greetings! >> >> I have an application that is written for x32 machines. However, we now >> have a few machines that are x64 and all is well when we are using the >> precompiled x32 DLLs provided by http://www.sqlite.org/download.html. >>

Re: [sqlite] x64 vs x32 DLL

"Stephan Beal" wrote... On Tue, Nov 4, 2014 at 9:20 PM, RSmith wrote: miniscule. On the downside, a 64-bit system uses 64 bit values for all registers even where 32-bit values could have sufficed, and so all internal looping through bits or register shifts take

Re: [sqlite] x64 vs x32 DLL

On Tue, Nov 4, 2014 at 9:20 PM, RSmith wrote: > miniscule. On the downside, a 64-bit system uses 64 bit values for all > registers even where 32-bit values could have sufficed, and so all internal > looping through bits or register shifts take longer, but generally by >

Re: [sqlite] x64 vs x32 DLL

On 2014/11/04 21:34, jose isaias cabrera wrote: Greetings! I have an application that is written for x32 machines. However, we now have a few machines that are x64 and all is well when we are using the precompiled x32 DLLs provided by http://www.sqlite.org/download.html. Changing the x32

[sqlite] x64 vs x32 DLL

Greetings! I have an application that is written for x32 machines. However, we now have a few machines that are x64 and all is well when we are using the precompiled x32 DLLs provided by http://www.sqlite.org/download.html. Changing the x32 DLLs to x64 DLLs, will it show any difference in

Re: [sqlite] Random locking errors using Sqlite.NET

Are you accessing data off the share as well? The Sqlite website is quite categoric that this is not a recommended mode of operation. Also given the database locks when a record is written it is entirely possible one user is locking the table. Cheers, Mike On Tuesday, 4 November 2014, Mike

Re: [sqlite] Random locking errors using Sqlite.NET

On 4 Nov 2014, at 5:45pm, Mike McWhinney wrote: > I am getting random locking errors during the execution of my program. The > program resides on a network and each client has a mapped share > with full read/write access to the folder as well as the .db file used by >

[sqlite] Random locking errors using Sqlite.NET

Hello, I continue to have random errors on SQLite.NET (ADO provider). I have the version 3.8.6 (System.Data.SQLite.dll with version 1.0.94.0). I am getting random locking errors during the execution of my program. The program resides on a network and each client has a mapped share with full

Re: [sqlite] sqlite3.8.7 crashes when creating an index with WAL mode disabled

On Tue, 4 Nov 2014 12:06:35 + Simon Davies wrote: > > And watch as it crashes when creating the index. > > From https://www.sqlite.org/compile.html: > > Important Note: The SQLITE_OMIT_* options do not work with the > amalgamation or with pre-packaged C code

Re: [sqlite] sqlite3.8.7 crashes when creating an index with WAL mode disabled

On 4 November 2014 04:17, RP McMurphy wrote: > Consider the following build cmd line: > > gcc -o sqlite3.exe -DSQLITE_OMIT_WAL sqlite3.c shell.c > > The build succeeds when using MinGW on Windows. > > Now start the built exe with a memory database: > > sqlite3

[sqlite] sqlite3.8.7 crashes when creating an index with WAL mode disabled

Consider the following build cmd line: gcc -o sqlite3.exe -DSQLITE_OMIT_WAL sqlite3.c shell.c The build succeeds when using MinGW on Windows. Now start the built exe with a memory database: sqlite3 :memory: And execute the following query: create table v(y);

Re: [sqlite] sqlite_column_table_name() and table alias name

Hi, any chance that this or a similar sqlite3_column_table_alias_name() were added to SQLite? TIA, Jose F. Gimenez ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Index without backing table

> On Mon, 03 Nov 2014 11:50:17 +0200 > Paul wrote: > > > > > Would be nice to have ability to store both key and payload in the > > > > index. (Let's call it index-only table) > > > > This could be a feature that sets some limitations on a table, > > > > like being unable to have