On 15 Jun 2016, at 3:44am, Wang, Wei wrote:
> Under the ANSI encoding environment, I created a table named TEST_PRODUÇÃO in
> the database.
All strings handled by SQLite, including the strings that make up SQL commands
like "CREATE TABLE ...", are Unicode strings. If you are constructing an
Hello SQLite Users, fyi ...
23rd Annual Tcl/Tk Conference (Tcl'2016)
http://www.tcl.tk/community/tcl2016/
November 14 - 18, 2016
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA
Important Dates:
[[ Attention!
Registration is open. Please have a look at
Under the ANSI encoding environment, I created a table named TEST_PRODUÇÃO in
the database. Then I opened this database with sqlite-tool. I ran the sql
statement to query all the tables and found the new created table was shown as
TEST_PRODU??O. Also this table could not be queried out using the
sqlite supports 'natural join' which allows you to omit the on clause for
well structured databases.
My database model is really a C# DataSet ( which contains DataTable, which
contain DataColumn and DataRow, (and this is superfluous, but row has a
reference to it's table and therefore the columns
On Tue, 14 Jun 2016 16:27:29 +
"Drago, William @ CSG - NARDA-MITEQ" wrote:
> Once the part has been grouped into a set (Matched=1) it receives a
> unique permanent serial number and the temporary serial number can be
> reused, so (Model, TemporarySerialNumber) doesn't have to be unique
> anym
One thing I would add is to try to populate your example database with
representative data - in fact, try hard to figure out what
representative data looks like, it informs many decisions. My
experience is that sometimes people assume that because something is
fast enough on their workstation, it'
On 14 Jun 2016, at 9:54pm, Smith, Randall wrote:
> Thanks for the ideas, Simon. Already good on the general principles. The
> approach of just periodically deleting all the indices and starting over from
> scratch with a massive, comprehensive re-profiling effort might work on a
> small pro
Thanks for the ideas, Simon. Already good on the general principles. The
approach of just periodically deleting all the indices and starting over from
scratch with a massive, comprehensive re-profiling effort might work on a small
project, an overstaffed one, one that doesn't change much, or o
> -Original Message-
> From: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users-
> boun...@mailinglists.sqlite.org] On Behalf Of James K. Lowden
> Sent: Tuesday, June 14, 2016 9:48 AM
> To: sqlite-users@mailinglists.sqlite.org
> Subject: Re: [sqlite] Trouble coding conditiona
On 14 Jun 2016, at 2:29pm, John Found wrote:
> you missed one small but very important
> detail:
>
> "When your application runs fast enough...
> **on the slowest possible computer you can run it**
> ...you are done."
A fair point. Thanks for the niggle. I might put it differently but cer
On Tue, Jun 14, 2016 at 8:47 AM, James K. Lowden
wrote:
> On Mon, 13 Jun 2016 19:11:29 +
> "Drago, William @ CSG - NARDA-MITEQ" wrote:
>
> > I need UNIQUE(B, C) only when E=0.
>
> A conditional constraint is evidence that you have two kinds of things
> represented in one table: those E=0 typ
On Tue, 14 Jun 2016 10:49:05 +0900
?? wrote:
> > On 13 Jun 2016, at 10:13pm, Richard Hipp wrote:
> >
> > The rename-is-atomic assumption is so wide-spread in the Linux
> > world, that the linux kernel was modified to make renames closer to
> > being atomic on common filesystems such as E
On Mon, 13 Jun 2016 19:11:29 +
"Drago, William @ CSG - NARDA-MITEQ" wrote:
> I need UNIQUE(B, C) only when E=0.
A conditional constraint is evidence that you have two kinds of things
represented in one table: those E=0 types that are identified by {B,C},
and the rest. They're represented i
On Tue, 14 Jun 2016 01:04:27 +0100
Simon Slavin wrote:
> When your application runs fast enough not to annoy you, you're
> done. If you're not willing to do step (1), don't bother with
> anything else.
Simon's entire post is excellent advice. To the OP: print it, and
frame it.
I would only
On Tue, 14 Jun 2016 01:04:27 +0100
Simon Slavin wrote:
> Got the principles ? Right. Now here's the procedure:
>
> 1) Delete all indexes.
> 2) Run ANALYZE.
> 3) Run your application.
> 4) Note the SQLite command which takes the most annoyingly long time.
> 5) Work out a good index which will f
15 matches
Mail list logo