the GROUP BY, then SUM(x) would presumably be the same number as x for every
row.
Did you mean this?:
SELECT foo, SUM(bar) FROM ... GROUP BY foo ORDER BY foo
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ays (except dates before the date
> you were actually born on, but those can't be greater than any of your
> birthday dates).
Another meaning for birthday is the the day in history where one was born, and
there is just one of these per person. More of
a characters, has something to do with searchability. On the
other hand, Tutorial D is much closer to SQL syntax, most alphanumerics. But I
just mentioned these for reference, and part of my inspiration; my proposal for
SQL should stand considered just in the context of SQL.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
nother verb less likely to pose problem would be easier to
> manage. What would you think of:
>
> SELECT ALLBUT foo FROM t ...
>
> Just a thought.
That could work as a simpler form where the result columns are simply input
columns and no derived expressions, but my proposal would k
s treated favorably by SQLite, I'll go
on
and propose it to other DBMS groups too, starting with Postgres.
Thank you in advance for the consideration.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
I'm not
aware of), but I think very useful.
For example, often users want to get all the result fields except for the
artificial fields just used to join the tables.
If SQLite's authors want to add such syntax as that, I support it, and other
DBMSs
Jay A. Kreibich wrote:
> On Sat, Sep 19, 2009 at 01:14:56PM -0700, Darren Duncan scratched on the wall:
>> 3c. I would like to have the option for SQLite to never have duplicate
>> unqualified column names; for example, if one said "foo NATURAL INNER
>> JOIN bar&
Alexey Pechnikov wrote:
> Hello!
>
> On Sunday 20 September 2009 00:14:56 Darren Duncan wrote:
>> 3b. I would like to have the option for SQLite to always operate using
>> 2-valued-logic rather than 3-valued-logic, meaning that NULL is simply
>> treated
>
upport duplicates and 3VL, and it generally
does what people actually want.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ssary, but otherwise that extra complexity isn't needed.
AFAIK, TAI can be determined in the first place simply as an offset from the
Unix integer time, I think. Various Perl modules exist to help; search for TAI
on CPAN. -- Darren Duncan
___
sqlite-
simple.
In
practice, it is simpler to deal with strings than characters, and asking simply
*if* a string is a substring of another, is a much simpler question, and LIKE
does that already. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
er than
"ON"?
In which case you also had a cartesian product between TABLEA and TABLEB.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
l
for the most recent prong that is expected to deliver useables the soonest,
maybe even in a month.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
s write up an easy to find policy page about the best ways to use or
not use the word SQLITE (any capitalization) so to work with his trademark.
See http://www.muldis.com/trademark_policy.html for my full version for
example,
and http://search.cpan.org/dist/Muldis-D/lib/Muldis/D.pm#TRADEM
Darren Duncan wrote:
> So I farmed out this question yesterday to another list I'm on, and got
> another
> And another response said:
>
>After having read a few of the responses, the original question strikes me
> as
> "very hard to answer".
>
>
; as it is commonly perceived/imposed by a
relational system (and after having covered that, it should go more or less
equally deep on (some) relational algebra). I honestly doubt whether such a
book really exists. Even Date's "Introduction to ..." doesn't strike me as
suitable becaus
tional Theory, author C.J. Date demonstrates how you can apply relational
theory directly to your use of SQL, with numerous examples and clear
explanations of the reasoning behind them. Anyone with a modest to advanced
background in SQL will benefit from the many insights in this book.
-- Darren
rates
how to better make use of the SQL DBMSs we already have.
-- Darren Duncan
P Kishor wrote:
> from the recent thread on "what is a relation," I followed Jay's
> suggestion and started reading up on relational division (an article
> by Celko at http://www.dbazine.com/
Rich Shepard wrote:
> On Mon, 27 Jul 2009, Darren Duncan wrote:
>> Object orientation has nothing to do with all this per se, though objects
>> can easily be mapped to tuples.
>
>A related issue is that object orientation is almost always used in the
> context of proce
ion values (rowsets)
as input and combines them to yield another relation value (rowset) as output,
such that member tuples (rows) are matched up with each other and catenated
into
a new set of tuples (rows).
So the term relation refers both to the contents of a SQL table *and* to a
process of c
.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo
that isn't the default. Also one of the advantages of SQLite in Perl vs other
DBMSs is that its drop-dead simple to install, and the bundling is part of that
experience. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.
or changes or
features for DBD::SQLite are expected to come out separately from and after the
stabilized switch to the amalgamation sources.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Than
some savvy is needed to
patch it for that migration.
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank you. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.o
stem.
Now that's not to say that some file systems aren't transactional; some are,
but
most and typical ones are't, and many that say they are only make meta-data
atomic not changes to the file content itself.
-- Darren Duncan
___
sqlite-user
e amalgamation too. the rest of you ideas are great also.
> excelent idea to use Audrey Tangs nameing convention.
>
> I have been stuck back at 3.4 for various issues.
>
> I do Perl and C and offer some help.
Okay and thank you.
-- Darren Duncan
_
place.
Matt, thank you in advance for a quick reply.
To everyone, please don't actually submit patches to me until I announce that
I'm ready to receive them, or just send them to RT as you already were.
-- Darren Duncan
___
sqlite-users mailing list
sqlite
, such that
they recommend using 1.13 instead, so there are binding-specific issues still
to
resolve as well. Hence doing the update well isn't as simple as just
substituting updated SQLite source files. -- Darren Duncan
Jim Dodgen wrote:
> I am having better luck with the amalgamation that
elf if any such
maintenance is needed, except on an experimental basis ... I'll also try
contacting the most recent maintainers about it. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listi
I'm now a step closer to being able to easily implement my Muldis D relational
database language over SQLite.
I'll hopefully be able to start testing in a few weeks, assuming that
DBD::SQLite et al / the Perl bindings are still functional under Mac OS X and
Linuxen with the new version.
-- Dar
in the same file. Triggers and views and
the
tables they work on need to be in the same file. -- Darren Duncan
Eric S. Johansson wrote:
> what's the general rule for deciding when to put multiple tables within a
> single
> sqlite db file? I think the answer is something like you put tables
rovide a collection of form fields where they enter
the
basic information and then you generate a SQL query from it. In that case, you
are *starting* with the tree as it were. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
htt
as these would still print
well, most people would see them without side-scrolling, the rest would only
side-scroll a bit.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
r the SQL standard
INFORMATION_SCHEMA. If SQLite is going to add any introspection features
for compatability with other DBMSs, it should go the information schema
route, or in SQLite terms, information database. -- Darren Duncan
___
sqlite-users mai
return the *first* row:
LIMIT 1
Note that rows in tables are not ordered (a table is a set of rows), so
there is no concept of newly inserted ones going at the end.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.o
e is providing itself, or compensate in the application-space for a
database implementation that lacks some of the relational database features.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ry key rather than
ROWID. This way, what columns exist and their values are always controlled
by you, and moreover your schemata would then be more portable between
different DBMSs. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.or
allow those 2 terms appearing together?) Does having
identical UNIQUE and PRIMARY KEY constraints lead to different semantics
than having just the PRIMARY KEY? I suggest changing SQLite about this. --
Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
o be disabled; they would just run
after the combined statement completes.
Note that my proposal is not the same as transactions, since you can have
triggers run between statements in a transaction and said statements are
not collectively atomic in the same way where no database state exists
bet
ngs
(modified if needed) but drops the bad behaviour.
Note that any warnings like this should be possible to turn off when the
user knows that their code is compliant and their string literals shouldn't
be checked anymore for similarity to column name
sly, there are no duplicate values at any time, so
the primary key constraint would remain happy.
-- Darren Duncan
Gregor Brandt wrote:
> Hi, thanks this is great. Of course I forgot to mention that the id
> is a primary key, so I get an error about duplicate primary keys.
>
tions should subjugate *all* DBMS
activity.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
omething completely different that I don't get.
I think what Joanne's asking is if it were possible to query what size the
database would become if it were vacuumed without actually vacuuming it.
Maybe as part of a cost analysis for whether to vacuum, or stats for the
user
distinguish one Joe from another.
My point still stands. Or my other point of adding a LIMIT clause to
UPDATE also stands if you want to create tables the second way.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Ralf Junker wrote:
> Darren Duncan wrote:
>
>> Ralf Junker wrote:
>>
>>> Can you suggest an alternative to a single reserved name to represent the
>>> column which uniquely identifies a database record under any and all
>>> circumstances?
>>
ne call rather than a column
name; eg use "RowID()" rather than "RowID". Then when using it in a
SELECT, you can say "RowID() as foo" in the select list where "foo" is
different than a normal table field. Such is how 'standard' SQL does it.
Any manager ap
ation details and can name tables and columns
whatever they want; saying they can't name their column "RowID" is a leaky
abstraction.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Gerry Snyder wrote:
> Darren Duncan wrote:
>> Clue stick coming up. There's a much simpler solution.
>>
>> You should be using relational difference instead, the MINUS keyword, whose
>> syntax is the same as UNION but for the keyword.
>>
> I think maybe yo
result should have 3 columns and 2 rows.
Rename c1,2,3 to taste, or adjust any other details as necessary.
If you wanted more info returned than that, then use the above in a
subquery which is joined with Fuzzyset.
-- Darren Duncan
___
sqlite-users m
e specifically I suggest a hybrid of what things like Yahoo
Groups provides, and a bulletin board. But I don't know if those tools
exist yet.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
iple tuples/rows. You are then
creating what are commonly called intersection tables, afaik, which
are common when implementing many-to-many relationships between
tables.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://s
provided with his new collation commit.
-- Darren Duncan
P.S. As another piece of full-disclosure, I'm in the midst of
writing the spec for an industrial-quality programming language,
named Muldis D, which is intended to replace SQL as the defacto
language of choice for relational databases. I'm
At 10:57 PM +0100 1/18/08, Zbigniew Baniewski wrote:
On Fri, Jan 18, 2008 at 12:32:36PM -0800, Darren Duncan wrote:
> If trailing spaces were supposed to be insignificant for an equality test,
then it should not be possible to define a string value containing
trailing spaces at all.
e other operator or
function like 'equal_when_trimmed( v1, v2 )' when you want various
exceptional comparisons.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
not having to check lengths and space pad
before each compare also makes the code simpler, and less buggy, and
it saves CPU cycles. A value equality test is a very common and
fundamental thing to do in a DBMS, and bloating that will have a big
performance impact.
-- Dar
in the intermediate value I mentioned (table of tables), but
even if it doesn't, a truly relational DBMS would have it.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
At 10:17 PM -0500 1/14/08, Griggs, Donald wrote:
Hi Duncan,
Regarding: " A DBMS accepting such queries isn't just a little
dangerous, its flat out wrong. I would ask what rationale there is for
this query not failing. -- Darren Duncan"
I'm not asserting that you hav
use
I would argue that this is a bug in the general case, where b does
not have the same value in every row of T. A DBMS accepting such
queries isn't just a little dangerous, its flat out wrong. I would
ask what rationale there is for this query not failing. -- Darren
Dun
no excuse not to notice.
So I agree with Richard's current versioning plan concerning this.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
something like that is worthy of a 3.6.0 version
number. Not just a minor version increase that would be more
suitable for minor changes or bugfixes. On the other hand, I can
understand if you save the larger increments for changes that are
user-visible and not just plumbing. -- Darren Duncan
ing generally useful, or too many cases
for why it would be a mis-feature whose use should not get the
encouragement from it being built-in.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
mplementing a
trigger routine or stored procedure that handles it. Or if you
really have to have the pragma, it needs to be off by default. --
Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
implemented this yet ... or maybe that was your intention.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ery
key or every column, and so all searches, which includes those on
which joins are performed, can/do look in what is otherwise indexes.
This is potentially slower for updates (or maybe not), but can be
faster for queries, depending on circumstances.
-- Darren Dun
this, for people who don't know, is that
this columnar thing is strictly an implementation detail. While
adopting it would be probably backwards-incompatible file formats,
the programmatic API and SQL et al wouldn't have to change a bit and
would remain compatible. -- Darren Duncan
, but no
announcements for 3.5.1 nor 3.5.2, which was part
of the reason I previously stated I hadn't
realized that 3.5.x had come out of alpha. --
Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
* Unlike most other SQL databases, SQLite does not have a separate
server process.
Actually, that's the only such typo I found on the front page (should
change to "SQL database engines"); all other occurrances of
"database" looked correct, also great news. But this is s
That said, this phrase can apply to any good open source software
that is already done, and isn't specific to SQLite. Or you could use
it anyway.
Or you could go with what Andy suggested.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
dividual table level. Note that I consider a database to be
the widest range of multi-table database constraints, such as foreign
keys, because all of its parts are always defined and live together.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
systems with remote storage.
If you're making an incompatible change anyway, then this rename
would be good for hand-in-hand with it, to help people migrating apps
from the old to the new; best to do all the incompatible changes at
once.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
)
Sort of like that.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
he result fields rather than SQL.
So I still recommend you do what you want in your presentation layer
rather than in the data layer.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
, iterating on the
count.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
cause problems, that foreign keys wouldn't help with; in theory, the
more generic format of triggers is a more complete solution, or more
specifically, free-form check constraints that can be comprised of
any query are a more complete solution. -- Darren Duncan
and it will work. Otherwise, if you have Mac OS X 10.4 Tiger or
later, a version of SQLite is also built-in as part of "Core Data".
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
ves
saying one or both are "UNIQUE" rather than "PRIMARY KEY". By
definition, there can only be one "primary".
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
), that is the
simplest option. -- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
m very poor at C and the regular maintainers of
SQLite would be able to do the job many orders of magnitude faster
than I could.
My contribution to the development of SQLite is mainly on the side of
design sugge
ch
easier to implement, I believe.
And if it will make a difference, I will even make a monetary
donation (as I can afford to) in order to sponsor its development
(though I would like to think that the benefits are compelling on
their own).
-- Dar
would help *that* problem.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
At 6:45 PM -0700 4/10/07, Darren Duncan wrote:
If one wants to still deny that rolling back a child without rolling
back a parent has no practical use, then we might as well not have
built-in SQL statements that are atomic, because that is exactly the
same end result for users.
If someone
At 6:05 PM -0600 4/10/07, Dennis Cote wrote:
Darren Duncan wrote:
I think that the question of what would be a reasonable minimum to
do now depends on what SQLite's current behaviour is when an
individual SQL statement fails that is part of a larger transaction.
Of course not. A reasonable
different applications is the more likely scenario where the
backwards compatability would help.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
t;main()" transaction. Users may want to try again, or try
going to a different page.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
At 12:33 PM -0400 4/9/07, Igor Tandetnik wrote:
Dennis Cote <[EMAIL PROTECTED]> wrote:
Darren Duncan wrote:
I will clarify that child transactions are just an elegant way of
partitioning a larger task, and that parent transactions always
overrule children; even if a child transaction c
At 4:38 PM -0700 4/5/07, Darren Duncan wrote:
To get this to work would basically involve having additional
journal files, with the original one being for the parent-most
transaction, and with an additional one for each transaction level,
or some such arrangement; the extra ones could have
ournal
file will still need all pre-change pages written to it too, but
intermediate-level files don't necessarily need this, or it can be
done, as the implementer wishes.
What would be the next best DB that does support this feature?
Ray
I don't know.
-- Darren
, with
SQlite 3, you don't get the second choice. --
Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
vidual SQL statements are atomic.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
Can you please provide a use case for your example, so we know what
you're trying to accomplish? That should help us to help you better.
-- Darren Duncan
At 12:08 AM + 12/14/06, RB Smissaert wrote:
I am moving my code away from VBA and transferring it to SQL.
There is one particular
you should start off with:
select a from mytable where (b=0)
... which is already valid syntax, and only add a bunch of "and
" when you actually have the "".
-- Darren Duncan
-
To unsubscribe,
to you if you are very careful, but often
they are more trouble than they are worth, and wherever possible, one
should use some other way to express the meaning of what they were
using NULLs for.
-- Darren
You can save your self a lot of grief by declaring all of your fields
to be NOT NULL and default the text fields to the empty string, ''.
Use '' rather than NULL when you don't have a name. Then you can
simply say "where foo=''". -- Darren Duncan
At 10:52 PM +0100 11/26/06, Danie
you get this in time.
We will be around probably all afternoon if you come later. Or email a
reply if you can suggest an alternate meeting time or when you might like
to come.
Good day. -- Darren Duncan
me columns are unique and some are repeated, perhaps try
splitting the tables into more tables that are related.
This, really, is what you should be doing first, and may very well be
the only step you need.
If you can't do that, then please explain in what way the data is repetitive?
-- Darren Duncan
to:[EMAIL PROTECTED]>
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <mailto:[EMAIL PROTECTED]>
-- Darren Duncan
itself using its journal file when your client
next is run. That said, if they manually edit
the database file with some other program, or
remove its journal file, then that could cause
problems, as that goes outside the SQLite code
and its ability to enforce ACID. -- Darren Duncan
ments; eg, 1 prepare() and many execute().
2. Don't commit for each row inserted but batch them so, say, you
commit once per 1000 rows.
Thanks,
Raj
-- Darren Duncan
At 08:40 +0800 16/3/06, Jiao wrote:
I want to be off this mail list, how to do it ?
Read the header of the email you sent to the list, as well as every
other list message; it says there "List-Unsubscribe" plain as day. --
Darren Duncan
.
-- Darren Duncan
301 - 400 of 571 matches
Mail list logo
