NULLs can be helpful 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 Duncan
-
trailing 'and',
so 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
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 parti
ay if individual SQL statements are atomic.
-- Darren Duncan
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
warnings
(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
ave to 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
sallow 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
ary 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@sqli
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
then just 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:
rt for 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-user
d be fine, 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
ll,
but rather you can just provide 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 li
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 t
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 versio
yself 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/mai
't in 1.13, 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
r suited (eg, with more C-fu) comes along and
takes my 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
___
en wrote:
> I'm for the 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 D
ieces in the file system.
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
es, so 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-user
hanges 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
n, but
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
ll go next.
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/mailma
Do bind parameters work for you if you replace the view with a subselect?
Does this work for you?
select * from (
select t1.*,
(select count(*) from song_artist t2 where t1.artist_id=t2.artist_id) as CNT
from artists
) where CNT=:PARAM
-- Darren Duncan
Cariotoglou Mike wrote:
>
fixes it; if you think it necessary I
can try asking the tester to try with the newer version.
Thank you.
-- Darren Duncan
--
Output from '/usr/ccs/bin/make':
cc -c -I. -I/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/auto/DBI
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
arren Duncan
Roger Binns wrote [to sqlite-us...@sqlite.org]:
> Darren Duncan wrote:
>> I would like to bring an apparent SQLite bug to the attention of the SQLite
>> core
>> developers as a ticket, where build fails on sun4-solaris-64int 2.10
>
> You'll find this is
yet let them through to the list so I'm forwarding a compilation of them for
the
latter's benefit.
-- Darren Duncan
1 of 2:
Original Message
Subject: Re: [DBD-SQLite] Re: [sqlite] SQLite bug ticket - build fails on
sun4-solaris-64int 2.10
Date: Sun, 3 Jan 2010 14:
ch I moderate) and I will let it in. Anyone
on
dbd-sqlite only that is interested in such issues should also join sqlite-users
so they can post to it directly.
-- Darren Duncan
Original Message
Subject: Re: [Fwd: Re: [sqlite] [DBD-SQLite] Re: SQLite bug ticket - build
fails on s
ird party comments in regards to whether I have reasonable
grounds to think there may be confusion between the 2 projects that could
affect
trademark matters.
Thank you in advance.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
since at
least Postgres 8.3, Postgres became stricter and stopped doing implicit casting
between disjoint data types, which would be required for [1='1'] to be true.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
you easily don't have all the
parts.
In your case, I would put everything, all your tables, in a single SQLite
database file, if you use SQLite, same as you'd use a single database if you
use
PostgreSQL or other options instead.
-- Darren Duncan
_
d want to support all 4 variants: 1..5, 1..^5, 1^..5, 1^..^5,
where a ^ means exclude that endpoint and its absence means include.
This is more flexible than SQL's BETWEEN, which I believe only covers one of
those 4 options.
-- Darren Duncan
___
s
lready supports, I would say is reasonable to support,
essentially an expansion of BETWEEN.
2. Generate a list of values, in which case you need an ordinal type, or a
closure to explicitly generate the next list element from a prior one. Such as
how one may generically define a "s
rg/sqlite-amalgamation-3.6.23.tar.gz was; it contains SQLite
3.6.22, not 3.6.23. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> and try again.
There is *still* a build problem, of a different kind.
With the current http://sqlite.org/sqlite-amalgamation-3.6.23.tar.gz, the
sqlite3.c file is 7.3MB and the sqlite3.h file is 3.7MB, and building fails
horribly. Each file is about 3.7MB larger than it was in 3.6.22.
-
. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Dennis Cote wrote:
> On 10-02-23 3:23 PM, Darren Duncan wrote:
>> Elefterios Stamatogiannakis wrote:
>>
>>> Madis is a extensible relational database system built upon the SQLite
>>> database and with extensions written in Python (via APSW SQLite
>>> w
Dennis Cote wrote:
> On 10-03-09 8:47 PM, Darren Duncan wrote:
>> (Incidentally, I *have* registered my trademark. But that is a non-issue
>> here.)
>>
> Darren,
>
> Aren't you required to put the registered trademark symbol, ®, on each
> use of your tra
n the same order.
Technically a table's columns aren't supposed to be ordered either, though SQL
makes them so.
And of course, dump the schema and tables in a mutually consistent order.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ry projects, or promoting
this project in various media and forums. Support is welcome in providing
significant financial sponsorship towards my further work, in which case you
have more of a say in its direction and priorities. But mainly I want to see it
get used to enrich projects and their
Congratulations on this milestone.
I also just realized now that you're adding WAL to SQLite; I have more to say
on
this, but that will be in a new thread.
-- Darren Duncan
D. Richard Hipp wrote:
> The first code check-in for SQLite occurred on 2000-05-29 14:26 UTC -
> ten year
er sees
that started the earliest so that then the WAL only has the corresponding
subset
from the earliest reader to the latest?
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
see anything in the WAL design that this couldn't be done without much
complexity.
Thank you in advance.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
this: the programmer never creates any indices at all. It's up
> to the database engine to decide how to do the searches most efficiently, the
> programmer just says how much memory it can use to do so.
What are some examples of the proposed SQL replacements that do this?
-- Darren Dun
Simon Slavin wrote:
> On 2 Jun 2010, at 1:14am, Darren Duncan wrote:
>
>> What are some examples of the proposed SQL replacements that do this?
>
> You might be interested in NoSQL, or in databases which have no schema: every
> piece of information is a property of an objec
Richard Hipp wrote:
> On Sat, May 29, 2010 at 5:42 PM, Darren Duncan wrote:
>> "3. Transactions that involve changes against multiple ATTACHed
>> databases are atomic for each individual database, but are not atomic across
>> all
>> databases as a set.
Richard Hipp wrote:
> On Thu, Jun 3, 2010 at 11:15 PM, Darren Duncan wrote:
>> Richard Hipp wrote:
> Partition means that one part of the database cannot communicate with
> another part. In the usual use of the CAP theorem, this means that the
> database is spread across multipl
e test
suite
depend on that the same one doesn't work for both versions.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ou could do is split your tables so each column you want
unique is in its own table and then you can make that a primary key. Not that
I
actually advise this since then you're just gaining a new problem or two in
place of the one you lost, such as ensuring there's
es, do you get the same failure or success? What if
you
take away the id column and only have the someint? (I don't recall if you said
the UNIQUE only didn't work if the primary key was used.)
Separately, as was reported in another reply, this issue is something you
sho
ains of the numeric, text, blob, etc types. This is how I see it, and put
in
those terms, SQLite is still strongly typed, but it is just more flexible than
some other DBMSs, those that don't support generic or union types.
-- Darren Duncan
___
sqli
.0" and then building and running "make
test". Building the same version pristine, without the "perl util/getsqlite.pl
3.7.0", passes all tests.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://s
Roger Binns wrote:
> On 07/21/2010 08:01 PM, Darren Duncan wrote:
>> Simply substituting in 3.7.0 causes a few new test failures for me with the
>> Perl
>> binding, DBD::SQLite, citing "disk I/O error".
>
> I can't speak for the Perl binding, but some o
I anticipate the solution may be to change how the DBD::SQLite tests work.
I'll report here once something's worked out.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
system is no longer updateable by the public; posting in the list can
cause an update there by a registered SQLite developer).
Please do not reply to me directly with your responses. Instead send them to
the forums or file with RT as is appropriate.
Thank y
ister-based virtual machine, which happened with release 3.5.5 on 2008 Jan
31. This was a completely backwards-compatible change, hence it came in a
0.0.1
version update. -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ase. This in contrast to the
approach of apply the journal or WAL and then don't change anything further;
the
latter is also important to support but users should have a choice between the
two options. -- Darren Duncan
___
sqlite-users mailing
Cory Nelson wrote:
> On Sun, Oct 10, 2010 at 8:51 PM, Darren Duncan
> wrote:
>> I think that it should be possible to configure SQLite to be strictly
>> read-only
>> in every respect, such that if with such configuration SQLite is told to
>> open a
>> data
toconf is the same as for 3.7.3; I would expect -autoconf to
be a proper superset.
2. Why does -amalgamation unzip to the folder name
"sqlite-amalgamation-3070400" but -autoconf untars to the folder name
"sqlite-3.7.4"? Why the inconsistent use of version formats?
-- Darren
Roger Binns wrote:
> On 12/07/2010 08:45 PM, Darren Duncan wrote:
>> I am also working with automated scripts, which now have to be updated to
>> use
>> either the new style or old style depending on the user-requested SQLite
>> version. (DBD::SQLite bundles a SQL
t lets you use all the power features you
have when querying data, anything a SELECT can do, and you can query the
database structure likewise. This is the way a relational database is supposed
to work. -- Darren Duncan
___
sqlite-users mailing
Wols Lists wrote:
> On 12/12/10 00:29, Darren Duncan wrote:
>> Nonsense. An information schema is a *good* thing, and is generally the
>> *best*
>> tool for introspecting a database. It lets you use all the power features
>> you
>> have when querying data,
Darren Duncan wrote:
> Wols Lists wrote:
>> Dunno how well that approach translates into a relational engine,
>> because Pick has several very non-relational quirks (every "row" MUST
>> have a primary key, the dictionary DEscribes, not PREscribes the FILE,
>>
likewise implement such tuples and relations
with
physical arrays behind the scenes.
Ordered lists and bags can be logically binary relations with index+value or
value+count attributes. (That is also the canonical way to do it in Muldis D.)
It is perfectly valid to nest tuples and relat
Wols Lists wrote:
> On 13/12/10 22:44, Darren Duncan wrote:
>> I am also very interested in these subjects.
>>
>> I believe that the relational model can accurately model anything in
>> the real world, and that this can be implemented in efficient ways,
>> wit
ables of that type and so on.
> Oh - and as an aside, Pick wouldn't need a transaction. The entire
> operation is atomic :-)
That's just a SQL-specific limitation. Other DBMS languages can or do make
that
atomic, and Muldis D does.
> To follow up on my basic mathematics comment - in a list of rational
> numbers, what is the ordinal position of the number "1"?
Normally there isn't an answer to this.
> The basic proofs of "what is infinity" rely on the fact that this
> question has no answer ...
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
tomic, but only provide an illusion of such,
and so can other DBMSs, including relational ones, as the implementations
provide. (And even then, operating systems are known to lie about whether data
has been physically written to disk when you fsync.)
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Wols Lists wrote:
> On 15/12/10 00:18, Darren Duncan wrote:
> The point I'm making is that a list doesn't contain any ordering *data*
> - it's inherent in the fact of a list. A list is an abstract concept. In
> Pick, I can store a data structure that IS an abstract
cares) where it
would be more on topic.
-- Darren Duncan
Wols Lists wrote:
> On 15/12/10 02:47, Darren Duncan wrote:
>> Wols Lists wrote:
>>> On 15/12/10 00:18, Darren Duncan wrote:
>>> The point I'm making is that a list doesn't contain any ordering *data*
>
SQL query to get that information as you did,
not that the way you did it is wrong per se, but just an alternate means to the
end.
I refer to http://search.cpan.org/dist/DBI/DBI.pm#Catalog_Methods :
column_info
foreign_key_info
primary_key_info
table
hat you want and it is the simplest solution plus
most
efficient in both performance and disk usage.
-- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ese
pairs like they were one number. You would then know at the end how to move
the
radix point since that was kept track of along with the number. -- Darren Duncan
> On Sat, Mar 26, 2011 at 8:15 PM, BareFeetWare
> wrote:
>> On 27/03/2011, at 12:39 PM, Patrick Earl wrote:
>&g
Patrick Earl wrote:
> On Sat, Mar 26, 2011 at 10:03 PM, Darren Duncan
> wrote:
>> You could store your exact precision numbers as a pair of integers
>> representing
>> a numerator/denominator ratio and then have math operators that work on these
>> pairs like th
nction you speak of and how does it differ from "sum"?
Also, it's better to call a function "mean" than "avg" if that's what is
intended, since there are other kinds of averages like "median" and "mode".
-- Darren Duncan
___
me thing,
which
is a string of bits. Maybe you're just wanting more operators so it is easier
to introspect or manipulate them? -- Darren Duncan
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ndpoint. You're just
saying that you can only have a z record when you have both corresponding x and
y records. I'm sure there are various business rules that this would
effectively model. -- Darren Duncan
___
sqlite-users mailing lis
new to
SQL, but I guess "INTEGER PRIMARY KEY" and "NOT NULL" aren't separated by
commas?
Having NOT NULL with a PRIMARY KEY is redundant, if not an outright
error. Defining something as a primary key is implicitly defining it
to be both not null and distinct. -- Darren Duncan
I believe that exactly the right circumstances to allow bound
parameters is all of the same places where literal values are
allowed, namely strings, numbers, nulls, etc. It does not make sense
to have bound parameters in any other situation. -- Darren Duncan
er's part; hopefully this will change
within 1-3 months.
-- Darren Duncan
even in that case it seems
wrong to pick the same kind as that which always means string literal.
-- Darren Duncan
er.apple.com/macosx/tiger/coredata.html
-- Darren Duncan
he most recent
code. This module does not come with Perl by default, but it is easy
to download from CPAN and install yourself.
-- Darren Duncan
nsert
statement is parsed once and then the actual data insert is
relatively little work and performs quickly. I believe this sort of
activity is what happens to implement the you wanted anyway. --
Darren Duncan
a compile-time option, since it would slow things down
for people that don't use it from the overhead.
-- Darren Duncan
At 10:42 AM -0400 5/7/05, basil thomas wrote:
We have not currently upgraded to version 3.xx even though there has
been many enhancements
that have made it an even bette
; eg, one can simply
mark a parent record as locked and the trigger will enforce that its
children are also locked at the same time.
That said, if this were a large database engine, there wouldn't be
any excuse to leave this feature out of the core.
-- Darren Duncan
D;
You use 'declare' to declare a variable. Also,
you only use 'set' when assigning the value of
another variable or expression. You do not use
'set' to retrive the value of a query, but 'into'
instead.
I don't know if SQLite supports this feature, tho
and so anyone
could sue the author if something went wrong when using it. I don't
know how true this is or not, but would like to see it addressed in
the answer.
-- Darren Duncan
ll my legal
concern out of thin air; there was a significant background to it,
even if it is an issue over which experts are divided.
Not FUD at all, in the malicious sense of the word anyway.
-- Darren Duncan
we stand to lose from such an
action? -- Darren Duncan
string, hence the
loss of the zero.
In that case, neither SQLite nor the Perl core is at fault, but the
intermediary between them, and hence the best solution is to fix that
so it at least always string-quotes (or ask Matt to do it). I ruled
out SQLite because you were using version 3 and explicitly defined
the field as a character string.
Meanwhile, you could follow the the workaround that DRH mentioned.
-- Darren Duncan
trict mode so that it only ever stores ints in int
columns. Like most databases do.
Matt, I would also appreciate it if a new DBD::SQLite was released
asap that embeds and is known to work well with the 3.2 series,
specifically 3.2.2.
Thank you in advance.
-- Darren Duncan
SQLITE 2.8.6... forgive the aging..
I believe that this is out of date and not applicable.
The SQLite 3.x line is not typeless and has distinct numerical and
text and binary data types.
Therefore it should be able to take columns declared as numbers and
sort them as such.
-- Darren Duncan
lease email me privately.
-- Darren Duncan
other than the
Makefile.PL, I didn't see any changes in them besides version number
updates. I looked in SQLite.xs and SQLite.pm.
-- Darren Duncan
you should be able to use that.
-- Darren Duncan
At 1:35 AM -0400 6/22/05, Al Danial wrote:
This table keeps track of how far two people ran in
a given week:
create table t(name, day, distance);
insert into t values("al", "monday" , 4.0);
insert into t values("a
I don't think that SQLite supports what you want yet.
As soon as the SQL:2003 "WITH RECURSIVE ... SELECT ..." syntax is
supported, you should be able to do what you want elegantly.
Meanwhile, you will have to do multiple selects to work with N recursions.
-- Darren Duncan
At
top or bottom of each subquery in order to
prevent losing the first/last row.
-- Darren Duncan
t too.
Hopefully someone else took that picture. -- Darren Duncan
x27;t want to use brackets ([]) as those are used by the
standard for array indices.
I suggest for simplicity that SQLite simply support single-quotes for
string delimiters and double-quotes for identifiers; clearly distinct
and simple.
-- Darren Duncan
101 - 200 of 640 matches
Mail list logo
