DBD::SQLite::Amalgamation 3.6.16 (the one Audrey released
yesterday) is unauthorized release, which actually is
nothing but repackaged DBD::SQLite 1.26_02 with original
::Amalgamation Changes. It won't be counted, so we don't
need to care. That said, we might want to convince her
not to include
install DBD::SQLite::Amalgamation and it
overwrites DBD::SQLite, but none of your code that uses SQLite needs
to change.
That's what it's there for.
Adam K
2009/7/30 Kenichi Ishigaki kishig...@gmail.com:
DBD::SQLite::Amalgamation 3.6.16 (the one Audrey released
yesterday) is unauthorized release
Hi.
1) We can rather easily see if a compiler exists or not, but
I think it too much to test if the compiler has some feature
or not. And, as DBI we require also requires a working compiler,
(false) unknown is not so bad (why do they have DBI when they
don't have a compiler? - probably they
As there're already several applications in the SQLite:: namespace,
it might be better to use (DBD::?)SQLite::Extension:: for the ones
to be loaded via load_extension(), and (DBD::?)SQLite::Module::
(or whatever) for the ones that adds a customized callback etc.
Kenichi
On Fri, 14 Aug 2009
Hi, Dmitri,
sorry but I don't think it's a good idea to apply your patch
right now. I haven't tested it yet, but SQLCipher's README
says 1) building via 'amalgamation' isn't supported, 2) we must
define SQLITE_HAS_CODEC, 3) we need to link against a OpenSSL's
libcrypt iwth sha256 support. That
Hi. Sorry that I had little time recently and didn't fix
the issue on sqlite numbers for 64 bit environments.
I tentatively disabled it as it is rather a big change
and might break other distributions' tests that expected
every bind param was a quoted text for sqlite. I'll look
into it again after
Hi. Please see the ExtUtils::MakeMaker's pod and try
perl Makefile.PL DEFINE=-DDBD_SQLITE_ENABLE_RTREE
or whatever. You'll get what you want. As for CPAN
clients, you can tweak a configuration option like
makepl_arg (permanently or tentatively).
Hope this helps.
Kenichi
On Thu, 26 Aug 2010
Hi Matthias,
2011/10/6 Adam Kennedy adamkennedybac...@gmail.com:
Hi Matthias
I may not be the best person to address this question to, as I'm just
the release manager and crotchety old fogie of DBD::SQLite.
The question is best addressed to the DBD::SQLite mailing list.
Hi. I don't usually use the threads module in my projects, but...
1) DBD::SQLite has several tests that use fork(), that means emulated
fork() (with ithreads) under Windows, and they've been working fine
for years.
2) DBIS/dTHR issue was fixed at DBD::SQLite 1.22_04 (released in
April, 2009) by
Applied both to the trunk.
Thanks,
Kenichi
2012/3/24 Yuriy Kaminskiy yum...@mail.ru:
Yuriy Kaminskiy wrote:
This cannot be right:
sqlite_set_result(pTHX_ sqlite3_context *context, SV *result, int is_error)
{
...
else if ( SvIOK(result) ) {
sqlite3_result_int( context,
Hi.
I don't think you can install DBD::SQLite with microperl. If you need
to use microperl, and you have a sqlite3 binary at hand, you'll
probably want to use system() (or backticks `` to get values):
./microperl -e 'system(q{ /path/to/sqlite3 db.file some sql statement })'
Refer to sqlite3
2013/5/11 Darren Duncan dar...@darrenduncan.net:
I remember, a few years ago around when this mailing list started, there was
some discussion about that one way to help make DBD::SQLite development
easier was to make use of something called alien, a project to help use C
libraries from Perl
up FreeBSD 9.1 VM now to
see what's actually happening, but any help would be appreciated.
Kenichi Ishigaki aka charsbar
___
DBD-SQLite mailing list
DBD-SQLite@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbd-sqlite
Hi.
It looks like those two errors come from different reasons. The first
one (of t/51...) can be safely skipped if DBD::SQLite is not compiled
with ENABLE_COLUMN_METADATA (see t/rt_40594...). You probably need to
update your manifest or run util/constants.pl (in the repository)
before you make a
14 matches
Mail list logo
