On 9/21/08, Alexander Batyrshin <[EMAIL PROTECTED]> wrote:
> Sorry for off-topic.
> What is main difference between DBD::SQLite and DBD::SQLite::Amalgamation?
Exactly what it says on the box. The latter uses the SQLite
amalgamation. The former doesn't. They both work exactly the same for
the end
Sorry for off-topic.
What is main difference between DBD::SQLite and DBD::SQLite::Amalgamation?
--
Alexander Batyrshin aka bash
bash = Biomechanica Artificial Sabotage Humanoid
On Sat, Sep 20, 2008 at 8:04 PM, P Kishor <[EMAIL PROTECTED]> wrote:
> I encountered this problem and solved it, so
Howdy folks,
I've been trying to test some cross compatability of sqlite, and having a heck
of a time with sqlites database .dumps and MiXeD CaSe based schemas. The
problem stems from an odd behavior of .dump to not quote identifiers when
outputting DDL, but to then quote the identifiers
On 9/20/08, Qianqian Fang <[EMAIL PROTECTED]> wrote:
> excellent! this works for me.
> thank you very much!
>
>
> Qianqian
>
>
> Kees Nuyt wrote:
> > You will have to transform the XML into an INSERT statement,
> > like this:
> >
> > INSERT INTO final (idx,enc,data) VALUES
OK, the mystery has been solved: didn't notice, that disk just reached
100% usage... :D
--
pozdrawiam / regards
Zbigniew Baniewski
___
sqlite-users mailing list
On Sun, Sep 21, 2008 at 12:26:32AM +0100, [EMAIL PROTECTED] wrote:
> You know what disk IO error means, right? Run scandisk
No, the disk is OK.
> and try dumping the database and restoring it to a new file.
Yes, I'm aware, that one can just create the database anew - but I was
asking, why
A 25mb file is nothing for SQLite; I vacuumed a 270mb test database a
few hours ago with no problems.
You know what disk IO error means, right? Run scandisk and try
dumping the database and restoring it to a new file.
On 9/21/08, Zbigniew Baniewski <[EMAIL PROTECTED]> wrote:
> It seems, it's
It seems, it's not possible to VACUUM a bit larger file? I tried to VACUUM
a database file of 25 MB size, containing 75000 records (about 20 fields
each). Unfortunately, each VACUUM attempt is interrupted with message:
SQL error: disk I/O error
No VACUUM allowed for such size?
Linux 2.6.26,
excellent! this works for me.
thank you very much!
Qianqian
Kees Nuyt wrote:
> You will have to transform the XML into an INSERT statement,
> like this:
>
> INSERT INTO final (idx,enc,data) VALUES ('rec1','001','line1
> line2
> line3');
>
___
ivo welch wrote:
> * SHOW columns FROM table--- would be a great addition, if only
> for compatibility with MySQL. Aside, it is easier to remember than a
> pragma.
MySQL's SHOW features are just an old MySQL-proprietary way of doing
introspection, prior to their adding support for the SQL
"ivo welch" <[EMAIL PROTECTED]> wrote
in message
news:[EMAIL PROTECTED]
> * Two simple functions would make SQLite much more useful to me are:
Be aware that you can extend SQLite with custom functions. See
sqlite3_create_function[16]
Igor Tandetnik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> The EXPLAIN QUERY PLAN keyword works, and I love it, but it's
> completely undocumented. How come?
http://www.sqlite.org/cvstrac/wiki?p=QueryPlans
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
On Sat, 20 Sep 2008 10:58:25 -0400, Qianqian wrote:
> hi
>
> I am quite new to sqlite, so, please forgive me if there
> is anything obviously incorrect.
>
> I created a table with the following fields:
>
>create table final(idx varchar(10), enc varchar(8), data varchar(4096));
>
>and I want to
ivo welch wrote:
> Sqlite is a wonderful program. A big thanks to its creator. As a new
> user, the following are nuisances, though, so I thought I would
> register these as simple suggestions:
>
> * SHOW columns FROM table--- would be a great addition, if only
> for compatibility with
Sqlite is a wonderful program. A big thanks to its creator. As a new
user, the following are nuisances, though, so I thought I would
register these as simple suggestions:
* SHOW columns FROM table--- would be a great addition, if only
for compatibility with MySQL. Aside, it is easier to
Alternatively:
pragma planner_ignore_index=1
On Sep 20, 2008, at 11:37 AM, Russell Leighton <[EMAIL PROTECTED]
> wrote:
> It would be very nice to have a way to explicitly control index use.
>
> I'm going to test my theory this weekend but I think if the index is
> not cached and the
hi
I am quite new to sqlite, so, please forgive me if there is anything
obviously incorrect.
I created a table with the following fields:
>>create table final(idx varchar(10), enc varchar(8), data varchar(4096));
and I want to import the following xml-type of data to this table:
rec1
001
I encountered this problem and solved it, so hopefully this will help
some other poor sod.
Audrey Tang's otherwise most excellent DBD::SQLite::Amalgamation
(bless her for this incredible package) was causing segmentation
faults for me while doing FTS3 searches on a RH ES3 Linux box. The
package
It would be very nice to have a way to explicitly control index use.
I'm going to test my theory this weekend but I think if the index is
not cached and the data large then the group by is faster without the
index. If this is the case I have a real issue. I need the index for
other queries
"suku249" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> Igor Tandetnik wrote:
>>
>> suku249 <[EMAIL PROTECTED]>
>> wrote:
>>> I need to convert dataTypes like int or string into sqlite3_value.
>>
>> Why? What are you trying to achieve?
>
> We are trying to implement fts3
I just wanted to point out that LiquiBase now supports SQLite.
LiquiBase is an LGPL Java-based tool for managing and applying
database changes. The general idea is that you specify each change
you need applied to your database in a file and each time you update
the database based on that file,
hi
I am quite new to sqlite, so, please forgive me if there is anything
obviously incorrect.
I created a table with the following fields:
>>create table final(idx varchar(10), enc varchar(8), data varchar(4096));
and I want to import the following xml-type of data to this table:
rec1
001
On Fri, Sep 19, 2008 at 10:47:33PM -0400, Russ Leighton scratched on the wall:
> What about the null values for the aggregation keys when I put a '+'
> to disable the index? Is that 'as designed'?
The "+" operator gets rid of type-affinities, and that can lead to
unexpected results. I'm
The EXPLAIN QUERY PLAN keyword works, and I love it, but it's
completely undocumented. How come?
On 9/19/08, Stephen Oberholtzer <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 19, 2008 at 12:36 PM, Giuseppe Costanzi
> <[EMAIL PROTECTED]>wrote:
>
>>
>> How could improve my code?
>
>
> Go into the
On Sat, Sep 20, 2008 at 08:45:16AM +0400, Alexander Batyrshin scratched on the
wall:
> Hello everyone,
>
> I gets strange result from this query on SQLite-3.6.2
>
> SELECT
> town.id, town_log.new_player_id, player.name
> FROM
> town_log
> LEFT JOIN town
>
We are trying to implement fts3 functionality without using the virtual table
implementation, So we are trying to implement three functionalities,
createTable(creates content,segement and seg dir table), InsertData (insert
data into the 3 tables) and selectTerms ( which selects data from 3
26 matches
Mail list logo
