On Thu, 2014-09-25 at 11:13 +0100, David Woodhouse wrote:
I suggested a couple of specific optimisations which the query planner
might be able to make, which should hopefully have benefits wider than
just my own use case. Are those not viable?
I'm preparing to commit a workaround to
On 10/09/2014 04:38 PM, David Woodhouse wrote:
On Thu, 2014-09-25 at 11:13 +0100, David Woodhouse wrote:
I suggested a couple of specific optimisations which the query planner
might be able to make, which should hopefully have benefits wider than
just my own use case. Are those not viable?
I'm
On 2014-10-09, 7:32 AM, Dan Kennedy wrote:
Got it, thanks for the explanation. Just to make sure that I
understand you correctly, is the clause MATCH '*l0l* *h4x*' getting
translated to MATCH 'l0l* h4x*'?
Yes, that's right.
Dan.
In that case, shouldn't the test in the original post have
All,
An automatic test system that I designed generates 25 data elements for each
unit tested. We test about 50 units/day. This data is currently being stored in
a csv file. I'd like to move this over to an SQLite database.
The question I have is, should I lump everything together in one table
Drago, William @ MWG - NARDAEAST wrote:
An automatic test system that I designed generates 25 data elements
for each unit tested. [...]
should I lump everything together in one table just like the .csv file
or should I create several smaller tables that group similar parameters?
I'm not sure
I wouldn't call it 'magical' if the definition is right on the field
declaration, and depending on the 'worth' of that particular bit of data
(Booleans in this case, and I've got absolutely zero concern to the actual
state of said boolean, but taking into consideration the typeless nature of
On 10/09/2014 07:23 PM, Sohail Somani wrote:
On 2014-10-09, 7:32 AM, Dan Kennedy wrote:
Got it, thanks for the explanation. Just to make sure that I
understand you correctly, is the clause MATCH '*l0l* *h4x*' getting
translated to MATCH 'l0l* h4x*'?
Yes, that's right.
Dan.
In that case,
Ryan,
That's exactly the kind of information I was looking for. Thank you.
-Bill
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
boun...@sqlite.org] On Behalf Of RSmith
Sent: Thursday, October 09, 2014 10:45 AM
To: sqlite-users@sqlite.org
Subject:
Clemens,
That's 24 columns per unit, not rows. There's no duplicate information.
Avoiding joins is something I considered. Thank you for confirming what I was
thinking.
-Bill
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
boun...@sqlite.org] On
I suggest you group columns into a structures that you are comfortable
with. I have a name, own a home, and have one car. Everything is singular
to me, an individual. So if I have a table Individuals, do I want 25
columns that encompass name, address, year, make, and model of my car, type
of
The question I have is, should I lump everything together in one
table just like the .csv file or should I create several smaller tables
that group similar parameters? I'm not sure what would normally be
done. I think the database is normalized properly in either case.
For SQLite, except
Hi,
Is it a reasonable assumption that immediately following a VACUUM command
the freelist_count will always be 0, or maybe 1?
Cheers,
Dave
Ward Analytics Ltd - information in motion
Tel: +44 (0) 118 9740191
Fax: +44 (0) 118 9740192
www: http://www.ward-analytics.com
concerned with organizational clarity and correctness than efficiency
From my personal experience, Sqlite is so bloody fast I simply side table
efficiency until it needs to be looked at. I can load 1.5 million name
address records (500 bytes each), a second table of 3 million records (same
On Thu, Oct 9, 2014 at 12:25 PM, Dave Wellman dwell...@ward-analytics.com
wrote:
Hi,
Is it a reasonable assumption that immediately following a VACUUM command
the freelist_count will always be 0, or maybe 1?
I think it should always be 0.
--
D. Richard Hipp
d...@sqlite.org
I'm assuming you're measuring something from each unit (I'm guessing
device?) out on the field?
Taking a quick glance at your table, I could see three tables being created
to normalize things out. You have particular units at a particular
location. That can be one table. Another table would be
Ok, thanks.
Ward Analytics Ltd - information in motion
Tel: +44 (0) 118 9740191
Fax: +44 (0) 118 9740192
www: http://www.ward-analytics.com
Registered office address: The Oriel, Sydenham Road, Guildford, Surrey,
United Kingdom, GU1 3SR
Registered company number: 3917021 Registered in England and
Hi,
I am new to SQLite. I am working on an app that I am developing and plan to
use SQLite as an embedded database. My Question - Does SQLite support
stored procedures similar to those in MS SQL Server etc. Any suggestions OR
pointers to information links woill be greatly appreciated. Thank you
Views, yes. Stored Procedures, no.
On Thu, Oct 9, 2014 at 1:04 PM, Omprakash Kolluri omkoll...@gmail.com
wrote:
Hi,
I am new to SQLite. I am working on an app that I am developing and plan to
use SQLite as an embedded database. My Question - Does SQLite support
stored procedures similar to
they can be implemented through registered extensions..(well no probably
not how you're thinking)..
I have a few functions to mimic MySQL functions like now(), curdate()
pretty simple
learned you can sqlite3_create_module() which is a virtual recordset...
but apparently can't add syntax
Don,
Thanks for weighing in on this. I'm going to experiment with the single table
solution and the 3 table solution below and see where I end up. The cream
always rises to the top.
Thanks to all who replied to this thread,
-Bill
CREATE TABLE UUT(
DatasetID INTEGER PRIMARY KEY,
On 2014-10-09, 11:09 AM, Dan Kennedy wrote:
On 10/09/2014 07:23 PM, Sohail Somani wrote:
On 2014-10-09, 7:32 AM, Dan Kennedy wrote:
Got it, thanks for the explanation. Just to make sure that I
understand you correctly, is the clause MATCH '*l0l* *h4x*' getting
translated to MATCH 'l0l* h4x*'?
On Thu Oct 09, 2014 at 11:29:49AM -0700, J Decker wrote:
they can be implemented through registered extensions..(well no probably
not how you're thinking)..
but apparently can't add syntax like 'EXEC ... but could make them be
like select * from (stored_proc) as an alias for exec (stored
On Thu, Oct 9, 2014 at 9:00 AM, sqlite-users-requ...@sqlite.org wrote:
Message: 6
Date: Wed, 8 Oct 2014 14:40:57 -0500
From: Nico Williams n...@cryptonector.com
To: General Discussion of SQLite Database sqlite-users@sqlite.org
Subject: Re: [sqlite] Detecting multiple CHECK failures
Hi,
Here is an example of stored procedure made in Python for SQLite.
https://pypi.python.org/pypi/sqlite_bro/0.8.7.4
I Hope it will help you figure out quickly if SQLite is ok enough for your
use-case.
Sheers,
___
sqlite-users mailing list
Thanks ALL. This has been very helpful
Om Kolluri
On Thu, Oct 9, 2014 at 1:19 PM, big stone stonebi...@gmail.com wrote:
Hi,
Here is an example of stored procedure made in Python for SQLite.
https://pypi.python.org/pypi/sqlite_bro/0.8.7.4
I Hope it will help you figure out quickly if
I use triggers, particularly INSTEAD OF INSERT triggers on VIEWs. The
values of the columns of the rows to be inserted are the stored
procedure's arguments. I use WHERE clauses judiciously to make up
for the lack of IFs. It works well enough.
I've used this in combination with recursive
Ben Lam wrote:
4. Right click on project, Add - Data - ADO.NET Entity Data Model;
Generate
from database; New Connection, in the 'Choose Data Source' window I don't
see
'System.Data.Sqlite Database File' as expected
Could you try removing the following line from the configuration file?
27 matches
Mail list logo
