wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL_2009
Obviously a bit biased toward PostgreSQL (since it's hosted there),
but it points out some fairly specific differences in features,
performance, etc. (I have no personal experience either way, but was
just curious my
or a read-only app, if I understand correctly. I believe that it's
okay to put that in a ramdisk, issues with chroot() aside.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
5c9a5
are pretty straightforward, so I could probably take a stab at this if you want.
What do you guys think?
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
ing the journal_mode).
Any additional flags or ways of doing this that I'm missing? Or is it a bug?
Thanks!
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
A freelist_count;' to 'PRAGMA page_count;' to make
your determination:
http://sqlite.org/pragma.html
Once the number of unused pages gets large enough compared to the
total database size, it might be an appropriate time to VACUUM.
--
Matthew L. Creech
_
apshot
and set journal_mode=WAL, no further tweaking of checkpointing or
anything, and log performance improved by ~30%.
Looking forward to 3.7.0!
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
#x27;d take that as a sign that LinuxThreads is
on its last legs.
Obviously there will always be some exceptions, but I'd imagine that
few of them are concerned with keeping those systems up to date with
the very latest SQLite.
--
Matthew L. Creech
___
sq
)
doesn't take a string - you did say it's pseudocode, I'm just
wondering if there's a problem with the arguments along those lines.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Mon, Mar 15, 2010 at 2:11 AM, Matthew L. Creech wrote:
>
> I'll give this a try tomorrow on a real device with journaling off,
> and see how much space it uses in /tmp with journaling turned off.
>
I ran some tests on a real device with a real database, and got the
lash on these
systems, so in my case "/tmp" is no different than the directory that
the database & journal are stored in. There's also not nearly enough
free memory to hold the small database, so I can't use temp_store =
MEMORY, unfortu
s in various locations, so I'd
need a programmatic solution - "move the DB somewhere else, VACUUM,
then move it back" won't work, unfortunately. :-)
Any tips are appreciated. Thanks!
--
Matthew L. Creech
___
sqlite-users mailing list
for when I do the real query. Seems like a pain for this
relatively simple scenario, but I can see how it'd be deceptively
easy-looking to optimize.
Thanks for the response
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.o
table.
My question: how can I optimize this kind of query so that it utilizes
both indexes, to grab the first [b] rows (ordered by time) which also
match [a]? Or am I just going to have to guess at which way will be
faster, and use "INDEXED BY" to force it? (The documentation says I
sh
ost=arm-unknown-linux-gnueabi
make install
If all you want is to run the sqlite3 executable, though, you can just
take the cross-compiled binary + shared-lib and throw them onto the
target. Note that you'll need to set LD_LIBRARY_PATH when running
"sqlite3" to
ation makes the delete run much
faster."
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
e way your example is
doing it, _every_ time through the loop it does an exec(), which
re-compiles the same SQL code (which is not a fast operation).
There are plenty of other examples floating around on this mailing
list, I'm sure - just do some digging.
--
Matthew L. Creech
g getdata() with this handle.
getdata() can just do sqlite3_bind_XXX() followed by sqlite3_step()
(and sqlite3_reset()), which will be _much_ faster than
sqlite3_exec().
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
n order of magnitude longer than the inner
SELECTs do on their own (i.e. without the GROUP BY which eliminates
rows with duplicate 'col1' values). Any ideas on how I could do this
more efficiently?
Thanks!
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
hared by other folks, do they each need to
> set this when they open or if I set it, it would apply to everyone that
> connects to it?
>
"page_size" will persist once you've done the VACUUM. "cache_size"
doesn't persist, but you can use "default_c
s doing wear-leveling behind the scenes, so throw in a
multiplier to account for that, and you'll at least get an
order-of-magnitude accurate idea of how long it'll last worst-case.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Thu, Jun 19, 2008 at 4:35 PM, Matthew L. Creech <[EMAIL PROTECTED]> wrote:
>
> I think this behavior is probably due to the way localtime() works in
> glibc. From what I've seen (at least on my embedded ARM-Linux board),
> localtime() only invokes tzset() the fi
ot a
good solution in SQLite, but as a start, you may want to try calling
tzset() yourself before each time you modify the flags, and see if
that fixes the problem.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
I'm really not sure - DRH would know more
about this.
The makefile does have a target to re-generate sqlite3.def on the fly,
but that's meant for Cygwin-based builds.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
clude that's only performed if
building in-tree. Let me know if you see any more problems.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
point of
using autoconf is to detect resources (header files, etc.) that aren't
portable. You can instead start with the pristine source, then:
cp Makefile.linux-gcc Makefile
make sqlite3.c
bypassing the configure script altogether. That should do what you want
--
Matthew L. Creech
s is under discussion right now: whether
we even need the specifically-sized types at all. If not, the
inclusion of and definition of those types may disappear in
the interest of portability.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
nfigure script is picking up standard headers like on
Linux which aren't supported in Visual Studio.
If you want to build the amalgamation on Linux without detecting
Linux-supported headers, you don't need to use autoconf - try:
1. Unpack the source tarball
2. cp Make
he amalgamation into a library and install it with the
headers (there are only 2). No idea about python integration, though.
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
utside of libsqlite3.so. We need to either rename it so
that it's part of the library's exported API, or do something
different in tclsqlite.c.
It's the only internal function this is a problem with, by the way -
you can check "nm -D libtclsqlite3.so" for all 'U' (u
make
>
Yeah, this was reported & fixed in CVS shortly after the 3.5.7 release:
http://www.sqlite.org/cvstrac/chngview?cn=4890
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
te) has targets to do the
same. It links the library itself with "-lpthread -ldl", which is why
you don't have to add those lines if you're just linking a program
against the shared library - gcc is instructed automatically by
libsqlite3.so to link them in.
--
Matthew L. Creech
cleaned up the header
generation, since it was using the default [empty] config.h rather
than the one output by the configure script. Let me know if you find
any other issues. Thanks!
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.
nd see if that works? (Or apply the diff at
http://www.sqlite.org/cvstrac/chngview?cn=4857 )
Thanks!
--
Matthew L. Creech
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
gt; select * from Images;
>
> i get no results returned to me. i just get returned
> to the prompt. is there anything that i missed? thanks
> again!!!
>
You're missing a bind for the first column (the imageID), and more
importantly, a c
34 matches
Mail list logo