e constant then you would also
rename this particular constant to match the new value, but the key thing is
you
have something easily look-upable that shows all the 4 are connected. -- Darren
Duncan
arately for the users' sake, while the actual columns have no significant
order in the database. Display order is also just one of many kinds of useful
meta-data, and storing that separately allows you to have whatever kinds of
meta
you want without complicating the core system. -- Darren Duncan
nerate 1,2,3=,3=,5 type sequences from
> self-joins but it seems a lot easier to do it in Delphi!
I agree with adding RANK, it is very useful.
-- Darren Duncan
On 2015-12-21 8:25 AM, Petite Abeille wrote:
>> On Dec 21, 2015, at 4:08 AM, Darren Duncan
>> wrote:
>>
>> If you want that feature, instead do it the better way that Postgres 9.5
>> did, which is as an extension to the INSERT statement in the form "ON
>&g
FUPDATE_.28.22UPSERT.22.29
Example:
INSERT INTO user_logins (username, logins)
VALUES ('Naomi',1),('James',1)
ON CONFLICT (username)
DO UPDATE SET logins = user_logins.logins + EXCLUDED.logins;
-- Darren Duncan
o find answers with less effort on
everyone's part if you do that. -- Darren Duncan
comment re
binary. -- Darren Duncan
On 2015-12-12 1:12 PM, Mark Hamburg wrote:
> Though to the extent that speed is proportional to data size, it would be
> good to use something other than hexadecimal to store UUIDs. Binary blobs
> would be the most compact, but ASCII85 encoding would
key fields where every record has a different value from every other record.
UUIDs have this quality in spades. It is even more important to index such
fields if you will either be searching/filtering on them or if they are the
parent in a foreign key constraint. This has always been the case, its not a
new thing. -- Darren Duncan
t to store, but just an approximation.
Per another suggestion, the best workaround is to use an INTEGER type instead,
and store an even multiple of whatever your smallest currency unit size is, eg
cents rather than dollars.
-- Darren Duncan
On 2015-12-11 6:21 AM, Frank Millman wrote:
>
ble change is significant; if the user can get a
different answer to any question about the database, including 'hidden' parts,
then the database is different, whereas if all questions they can ask return
the
same answer, then the "arbitrary row" should be the same row. -- Darren Duncan
'/'tuple' there
are various places in the application that specifically dispatch different
logic
depending on those values, whereas with data, such as an enumeration of country
names, it would not be the case.
-- Darren Duncan
On 2015-11-25 7:14 AM, Simon Slavin wrote:
> On 25 Nov 2015, at 2:2
sql.org/docs/9.4/static/datatype-enum.html . Do what Simon
says. I don't see a problem here. -- Darren Duncan
On 2015-11-24 3:24 PM, Domingo Alvarez Duarte wrote:
> If we do that we'll be repeating the same string on every column and need a
> string comparison, with postgres enum type
On 2015-11-18 2:05 AM, Dominique Devienne wrote:
> On Wed, Nov 18, 2015 at 10:58 AM, Darren Duncan
> wrote:
>
>> On 2015-11-18 1:27 AM, Yuri wrote:
>>> I agree they can be beneficial, but not in all cases. Depends on what you
>>> do. It
>>> wou
operation, which is my point.
-- Darren Duncan
On 2015-11-18 2:06 AM, Darren Duncan wrote:
> On 2015-11-18 1:58 AM, Dominique Devienne wrote:
>> On Wed, Nov 18, 2015 at 10:17 AM, Darren Duncan
>> wrote:
>>
>>> Deferred constraints are definitely a benefit.
&g
On 2015-11-18 1:58 AM, Dominique Devienne wrote:
> On Wed, Nov 18, 2015 at 10:17 AM, Darren Duncan
> wrote:
>
>> Deferred constraints are definitely a benefit.
>
>> They allow you to express constraints otherwise not possible, for example
>> that a record ma
On 2015-11-18 1:27 AM, Yuri wrote:
> On 11/18/2015 01:17, Darren Duncan wrote:
>>
>> Deferred constraints are definitely a benefit.
>>
>> They allow you to express constraints otherwise not possible, for example
>> that
>> a record may exist in table X if an
t for enforcing constraints. SQL
immediate
constraints break this ease of use.
-- Darren Duncan
on a failure we already know happened. This add-on
could also be a compile-time option to exclude if desired. -- Darren Duncan
On 2015-11-17 2:32 PM, Richard Hipp wrote:
> On 11/17/15, Yuri wrote:
>> This message always leaves the user wondering: "Which constraint?"
>>
is subscribed with a
different address than they are sending the scams from. The responses are too
quick to just be an archive scrape, maybe. -- Darren Duncan
On 2015-10-18 2:31 PM, jose isaias cabrera wrote:
>
> No, they are not. The emails are coming straight from theAlexa
post I replied to today.
Someone on the SQLite mailing list has been hacked and/or a phisher has
subscribed to the list.
-- Darren Duncan
There's also the obvious question of, what SQLite version are you using on each
OS? -- Darren Duncan
On 2015-10-17 12:57 PM, Simon Slavin wrote:
>
> On 17 Oct 2015, at 8:53pm, Lucas Ratusznei Fonseca gmail.com> wrote:
>
>> I am using sqlite for years with my software on Window
the newest SQLite at the
time, and SQLite itself should be released on its own schedule. Also, while
some projects like 6-month feature releases, that is far from a concensus. I
know a bunch that like annual releases, Postgres and Perl for example, which
work well. -- Darren Duncan
On 2015-10
On 2015-10-08 6:03 PM, Richard Hipp wrote:
> On 10/8/15, Darren Duncan wrote:
>>
>> 2. If two successive versions have an overlapping but not equal API and
>> file format, meaning that a subset of data files but not all of such
>> readable or
>> wri
, or such as for marketing reasons.
Richard, does that still seem to describe your intentions?
-- Darren Duncan
On 2015-10-08 6:38 AM, Richard Hipp wrote:
> Several users have proposed that SQLite adopt a new version numbering
> scheme. The proposed change is currently uploaded on the "draft
the change to not
break anything / be fully backwards-compatible, whether due to being a new
feature or a bug fix.
-- Darren Duncan
On 2015-10-07 1:13 PM, Scott Robison wrote:
> Really, the SQLite3 versioning isn't that far off from Semantic Versioning.
> Instead of MAJOR.MINOR.PATCH w
in another one; the inner determines the latest time per
currency-day and the outer one looks up other info related to it.
The above example should also perform very efficiently, besides being reliably
correct rather than just accidentally correct.
-- Darren Duncan
one of
its key features.
-- Darren Duncan
e. If a DBMS' standard database dump includes details
that can't be gleaned from the DBMS' INFORMATION_SCHEMA, then the latter isn't
sufficiently exhaustive, and would need to be extended in order for an
updateable version to fully replace distinct DDL. (Case in point, MySQL is
deficient in this way, I know from experience.) -- Darren Duncan
the C style like
most popular application languages and functional language style. I will make
an announcement when you can run it, hopefully within about 2 months. -- Darren
Duncan
On 2015-08-29 2:55 PM, Domingo Alvarez Duarte wrote:
> I like the overall idea but of Muldis D (like the aquam
ble to do all catalog/code manipulation as
data, or homoiconicity. In fact this is a central pillar of my own Muldis D
project, an industrial strength programming language with fully integrated
database functionality. -- Darren Duncan
dern days even when supported, unless its the only option. AFAIK,
INSERT...INTO was only ever for use within a SQL stored procedure for assigning
to a lexical variable. At least I've never seen it used the way you introduced.
-- Darren Duncan
Have a look at PostgreSQL 9.4 as well and its new JSONB data type. Gives you
the goods of relational and hierarchical databases in one place, including the
querying and indexing. -- Darren Duncan
On 2015-07-13 5:43 PM, Hayden Livingston wrote:
> Is there a concept of a schema-less J
a clean-room scenario, you're just looking at your
data
file.
-- Darren Duncan
On 2015-06-29 3:19 PM, Darren Duncan wrote:
> I think a WhatsApp database is analogous to a data file and falls outside the
> concept of reverse engineering here.
>
> If say Microsoft Word had legalize aga
just the program.
At the very least, since WhatsApp databases store user data, it should be
reasonable to understand their structure in order that users can extract their
own data from them reliably.
-- Darren Duncan
On 2015-06-29 6:42 AM, John McKown wrote:
> On Sun, Jun 28, 2015 at 7:24
programming language,
but subsequent implementations will cross-compile as possible to existing SQL
DBMSs so the work in those engines can be leveraged as possible. The reference
is standalone so I am not limited by what current DBMSs support to make it work.
-- Darren Duncan
On 2015-06-18 2
than just SQLite specifically. That also means that the SQL alternative would
in practice be a language family itself, assuming multiple implementations,
though hopefully they would be a lot more consistent with each other than the
SQL family languages have ended up being. -- Darren Duncan
On 201
anging whatever it wants to do
to implement the over-all expression efficiently, in fact a DBMS may even have
an easier time of it.
Don't get me wrong, a new language can have these qualities and still look
familiar to SQL users, its not like it means using APL etc.
-- Darren Duncan
circumlocution. That is how you would simplify the transition
and re-utilization of existing code. The good alternative would actually be
easier for a DBMS to implement also without losing any power.
-- Darren Duncan
On 2015-06-17 11:52 PM, ajm at zator.com wrote:
> Indeed, I'm ag
alternative. I also
believe
the world is ripe to have SQL alternatives, its just a matter of ones appearing
that are compelling to users for real work and not just an academic exercise.
The fact we're still generally with SQL means this hasn't happened yet, but
that
doesn't mean it won't.
-- Darren Duncan
s for both routines and relations
(tables) etc are arbitrary/variable depth like you propose, like either the
Unix
file system or like programming languages such as Perl or C# or others.
Note that Muldis D and Andl have some influences in common, but David beat me
to
market as it were with an executable.
-- Darren Duncan
above example should make more clear what's going on.
-- Darren Duncan
On 2015-06-15 5:46 PM, Christopher Vance wrote:
> With a relational model you have a choice between relational calculus or
> relational algebra. SQL does one of them.
>
> I have used a language which did the oth
Like most mailing lists about open source software, list archives are visible
to
the general public, which is what I think should be the norm. Generally
restrictions to members just concern posting, its a simple way to keep spam
out,
one has to confirm an email address to post. -- Darren
More like It'll be out in time for Christmas, where the specific year isn't
mentioned. -- Darren Duncan
On 2015-05-23 11:09 AM, Mikael wrote:
> This sounds like it means we'll have it 2.5-5 years then.. so 2018 maybe,
>
> Sounds about correct? :)
>
>
> 2015-05-23 23:06
sertion has no impact on their final values (in the absense of triggers).
In that respect uuids can be better than auto-inc because you lose those
coupling problems. On the other hand uuids themselves should be used very
sparingly, and I haven't really seen a reason to use them yet.
-- Darren Duncan
o also can be rolled back and repeat.
That's all that standard SQL/etc sequence generators are, regular user data,
and
one shouldn't be fooled into thinking they are something else.
-- Darren Duncan
On 2015-05-20 4:21 PM, Keith Medcalf wrote:
> All relational database engines store configuratio
o grasp that each entire tuple/row in a
relation/table is by definition its own identity. If no subset of
attributes/columns is a key, the entire tuple/row can be used to identify which
tuple/row you're talking about. -- Darren Duncan
for example. This can't be
counted on for all BLOBs, but can work for some. Meta-data is good to have. --
Darren Duncan
On 2015-05-09 3:20 AM, Richard Hipp wrote:
> On 5/9/15, William Drago wrote:
>> All,
>>
>> Say you encounter a blob in a database. There's no way to
>>
nner query in the FROM clause
to generate the fields you want to sort on, and then ORDER BY on them in the
outer query. -- Darren Duncan
On 2015-03-31 5:31 PM, R.Smith wrote:
> On 2015-04-01 01:50 AM, Bart Smissaert wrote:
>> Say I have a table with 3 fields. Depending on a value in fie
If you design your database schemas such that, where possible, corresponding
columns have the same names in all tables, and you do natural joins, the
problem
will basically go away. -- Darren Duncan
On 2015-03-16 9:16 AM, Drago, William @ CSG - NARDA-MITEQ wrote:
> All,
>
> Some of
plications, and the same arbitrary
user-defined types you can use in applications can be used directly in
databases, no "mapping" required. I hope to have a first version executing in
about 2 months. -- Darren Duncan
with duplicate
data in the source, find or handle with SELECT GROUP BY etc rather than trying
conditional INSERT logic or what have you.
-- Darren Duncan
So far so good. I only got one copy of your test message. I also sent my own
message to just sqlite-users at sqlite.org and it was bounced as expected. --
Darren Duncan
On 2015-03-02 8:14 PM, Mike Owens wrote:
> Okay, I blocked the sqlite-users at sqlite.org address in the to address
&
is reminding
people
to pay attention until the issue as a consequence goes away. Thus any explicit
Reply-To headers can be left unmunged by the list server. -- Darren Duncan
On 2015-03-02 7:10 PM, Mike Owens wrote:
> The problem is that this is the very bone of contention in the re
iling lists. We'll try to stay as agnostic as possible, but our
>> biases may still peak through.
>>
>
> That's as much as I'll say about that.
Well it doesn't have to be complete munging, rather just enough munging to
remove references to the old mailing list name. -- Darren Duncan
On 2015-03-02 6:08 PM, Mike Owens wrote:
> On Mon, Mar 2, 2015 at 5:24 PM, Darren Duncan
> wrote:
>> As near as I can tell, the Reply-To header from this list only contains
>> sqlite-users at mailinglists.sqlite.org and does not also contain
>> sqlite-users at sqlite.org
On 2015-03-02 3:04 PM, R.Smith wrote:
> On 2015-03-03 12:42 AM, Darren Duncan wrote:
>> I think that what needs to be done is for each foo at sqlite.org to return an
>> error/undeliverable message if someone sends a message to it, citing that all
>> messages mu
I think that what needs to be done is for each foo at sqlite.org to return an
error/undeliverable message if someone sends a message to it, citing that all
messages must be explicitly sent to the corresponding
foo at mailinglists.sqlite.org. That should handily solve the problem. --
Darren
On 2015-02-28 3:15 AM, R.Smith wrote:
> On 2015-02-28 05:02 AM, Darren Duncan wrote:
>> I'm seeing a lot of message duplication too, but the ones I see are due to
>> someone putting the list address twice as a recipient.
>>
>> For example a bunch of the "PhD stud
qlite.org .
But both of those are aliases for the same list.
Whoever is doing this, sending your messages to both, please stop, just send to
one, and then people would get one copy.
-- Darren Duncan
On 2015-02-27 12:09 PM, Peter Aronson wrote:
> I've seen it too. All of the duplicate messages ap
I recall that
http://blog.heapanalytics.com/postgresqls-powerful-new-join-type-lateral/ shows
how Pg 9.3's LATERAL join is useful in practice, as it lets you do in
declarational SQL what you may have needed procedural code for before, in which
case it is an improvement. -- Darren Duncan
nce
generator first in its own transaction and remember the value, then use that
remembered value in your main transaction that you explicitly do afterwards.
Do you understand what's going on now?
-- Darren Duncan
___
sqlite-users mailing list
sqlite-u
itself, as that practice
generally leads to huge security problems / SQL injection (although if your
language is strongly typed an int wouldn't do it, but a string would). -- Darren
Duncan
On 2014-11-04 1:47 PM, Drago, William @ CSG - NARDAEAST wrote:
All,
I've been pulling my hair out trying
-05')
where the content of the IN would have the first item and the last item of the
list, but that's it? Thanks.
You're talking about a range/interval.
In SQL it is spelled like this:
BETWEEN '2014-01-01' AND '2014-01-05'
-- Darren Duncan
changed by accident.
-- Darren Duncan
On 2014-09-06, 7:22 PM, Richard Warburton wrote:
Hi,
Brief:
Should transactions be used for ensuring consistency between multiple
queries? And if so, after I've finished is there a reason why I should not
call commit?
Background:
I'm using SQLite for a web
other value, which is how it is supposed to be.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
A common logical error that may be affecting you is, do your dates include a
time portion or are they just year-month-day? If they include a time portion,
then records from Dec 31 likely won't be counted as your 'between' arguments may
be equivalent to '2013-12-31 00:00:00'. -- Darren Duncan
On 2014-08-31, 9:35 PM, Darren Duncan wrote:
On 2014-08-31, 9:10 PM, jose isaias cabrera wrote:
SELECT cust, sum(ProjFund), sum(Xtra8), coalesce(billdate,bdate) as t FROM
LSOpenProjects WHERE billdate BETWEEN '2013-01-01' AND '2013-12-31' OR bdate
BETWEEN '2013-01-01' AND '2013-12-31' GROUP
), t FROM (
SELECT cust, ProjFund, Xtra8, coalesce(billdate,bdate) as t FROM
LSOpenProjects WHERE billdate BETWEEN '2013-01-01' AND '2013-12-31' OR bdate
BETWEEN '2013-01-01' AND '2013-12-31'
) x GROUP BY substr(t,1,7), cust;
-- Darren Duncan
___
sqlite
Sorry, the count thing was actually Mark Halegua's question. -- Darren Duncan
On 2014-08-27, 8:58 PM, Darren Duncan wrote:
On 2014-08-27, 8:41 PM, Keith Medcalf wrote:
this may seem like a small issue, but I'm not sure if the solutions I've
found on the web will do what I want in a low memory
ather than hard.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
parameters in a temporary
table and then use that for the join in a subsequent select.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Is something wrong with the configuration of this sqlite-users list?
A message of subject "Porting SQLite to plain C RTOS" was allowed and
distributed through it this morning with attachments.
Not only attachments, but about 5MB of attachments.
-- Dar
. There's no
reason that table names can't be values in principle. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
there is yet another significant way
in which SQLite is more powerful than MySQL (but not PostgreSQL), the WITH
support being another, and subjecting data definition to transactions is another.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-u
on is like
that too. I have seen several others that are on the realistic side.
But a counter-example is a show I saw where they had "programming code" but it
was actually HTML source, which really shows those ones didn't do thei
ot;. Whereas, "float" is best suited for the name of a
concrete type, like with "integer" and "ratio". (Well strictly speaking all of
these could be abstract types, but the latter set are more specific in meaning,
and in particular "ratio" and &qu
ith a join condition saying which fields you
want to be used for matching in the join, and also replace the "select *" with a
specific list of fields you want to match up for the union.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-u
require creation of separate schema objects, while
someone with read-only access to a db can use WITH, especially beneficial for
ad-hoc reports. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin
t have WITH RECURSIVE without WITH. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
e sponsor is now indicating that they want to go with WITH
RECURSIVE. So the CONNECT BY branch has been closed and we are starting to
work on a WITH RECURSIVE implementation.
That's great news! This will be a serious step up in feature set for SQLite,
both in ease of use and power, I look forward
be taking up with the makers or a users
group of the wrapper for help. You should be asking in some support forum
specific to Entity Framework about this problem. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http
today don't have the precondition of a "transaction" being
active to use them, so on their own "savepoint" is like a generalization of a
"transaction". -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
at don't lock the whole database they may be useful with.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On 2013.10.15 10:34 PM, Petite Abeille wrote:
On Oct 16, 2013, at 7:20 AM, Darren Duncan <dar...@darrenduncan.net> wrote:
On 2013.10.14 11:58 PM, Sqlite Dog wrote:
seems like SQLite is not checking trigger SQL for invalid column names
until execution?
What you describe sound
to reverse it, at least for default semantics. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
support, but rather a representation of
SQLite metadata as tablevars. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
hough some of that is best to have in practice.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
I don't think that being ACID and SQL compliant is the definition of a DBMS, far
from it. While it is true that typically anything which is ACID and SQL
compliant is a DBMS, lots of things can be a DBMS without being either ACID or
SQL compliant. See dBASE for example. -- Darren Duncan
support views, you could define views having the names that
the users want. In fact, that's what views are for, letting different users
have different interfaces to the same database.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users
something like this:
execute format( 'SELECT %I FROM table that has that columnName',
(SELECT columnName FROM columnNameTable WHERE condition how to select limit
1) );
But I don't know if SQLite can do that in SQL; you might have to use the host
language.
-- Dar
about
subqueries before you talk about joins or grouping. On the other hand, I
suppose from an explanation point of view, a subquery in the SELECT list could
actually be a simpler thing to explain to a SQL newbie, so maybe that's why it
is first. -- Darren
where the former can produce a
fractional result while the latter guarantees a whole number result.) The
pragma is a bad idea. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
easily to use your app.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
, and a very appropriate way to bring
in many kinds of extra functionality, such as regular expression support. And
I'm glad an extension for that is provided now, which gives much more power to
type constraint definitions. -- Darren Duncan
ALUES ("' +
dataGridView1.Rows[i].Cells["Column1"].Value + "', '" +
dataGridView1.Rows[i].Cells["Column2"].Value + "', '" +
dataGridView1.Rows[i].Cells["Column3"].Value + "', '" +
dataGridView1.Rows[i].Cells["Column4"].V
requestor. Say for example and end user of the DBD::SQLite
Perl module that wants to pull in the latest SQLite version to build it against,
without having to specify a version. We shouldn't expect such a user to have a
fossil client, they should just be able to pull the amalgamation tarball over
th
Igor Korot wrote:
Darren,
On Tue, Oct 23, 2012 at 8:53 PM, Darren Duncan <dar...@darrenduncan.net> wrote:
You should not have an application installer, at all. Instead, you can ask
the question on where to store the database when the user opens your
program. Or better yet, your appli
, your application should support having multiple
databases per user, even if they may typically just use one. If users open your
program directly and not by double-clicking on a database file, you could
automatically bring up a prompt to make a new one, as if they used th
eded a nested transaction in the first place, but rather just the one
outer transaction 1, or you might have wanted an autonomous transaction, which
is different, depending on what you want.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
,
you'll have Windows 8 on your next trade-up, as it comes out later this month.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
101 - 200 of 571 matches
Mail list logo
