[Dxspider-support] SQL database support

Dirk Koopman djk at tobit.co.uk
Sun May 13 22:33:10 CEST 2007

Michael Chen wrote:
> I am looking for a way to store the spots into a MySQL table.  I look
> through the mailing list, but found no clue. There was a message about
> SQL support in Jan. 2006, but don't seems to have further info. (BTW,
> it would  be great to enable the search for mailing list).
> I looked through the source code, and found there were following lines
> in DXVars.pm
> # are we doing xml?
> $do_xml = 0;
> # the SQL database DBI dsn
> #$dsn = "dbi:SQLite:dbname=$root/data/dxspider.db";
> #$dbuser = "";
> #$dbpass = "";
> and also, there is a  DXSql.pm and a DXSql directory.
> Are these codes completed, and any documentation available on how to
> make use of them?

I am a afraid that you are essentially on your own here. It is very 
experimental. There is some database code in there and it does store 
spots. It doesn't do much else. Have a look at the DXSql directory to 
see what is required. You should find that it sets itself up automatically.

Please email me off list for (not much) more information.

I use it mainly with a Sqlite 3 database which satisfies my 
requirements. On speed tests, there seems little difference in speed 
between pure perl, Sqlite or MySql other than MySql uses all of the 
available RAM to do what it does.

There are actual disadvantages using a SQL database for some of the more 
complex sh/dx queries that are possible. To the extent that I am 
seriously think of taking the SQL interface out of sh/dx (currently, if 
you enable $do_sql, it will use the sql database for sh/dx). This is one 
of the reasons that it has not been developed. Basically, it doesn't 
give me enough extra to be worth the pain of sorting out the problems.


More information about the Dxspider-support mailing list