Puneet Kishor wrote:
Fred Williams wrote:
I think what is being looked for here is information available from many
commercial databases. There are elaborate "System" tables containing the
entire database structure down to the finest detail including table
formats,
relationships, triggers, stored
Fred Williams wrote:
I think what is being looked for here is information available from many
commercial databases. There are elaborate "System" tables containing the
entire database structure down to the finest detail including table formats,
relationships, triggers, stored procedures, and etc.
ill Leshner [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 11:08 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [sqlite] Dumping and importing database via Perl
> DBD::SQLite
>
>
> Puneet Kishor wrote:
>
> > One possible way to make this easier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 25 May 2004, Puneet Kishor wrote:
That is nice. I will definitely use this approach for myself. Many thanks for
your helpful response.
Actually, based on some stuff in the digest that I hadn't seen before,
I've made the code a little nicer:
Puneet Kishor wrote:
One possible way to make this easier
would be to actually have an alternate "schema table" with such
information in it for every table. That way one would query _that_
alternate "schema table," and instead of getting the SQL statement used
to form a given table, one would
D. Richard Hipp wrote:
Puneet Kishor wrote:
Also, afaik, there doesn't seem to be any "easy" facility to
reconstruct the schema...
The schema is exactly reconstructed as follows:
SELECT sql FROM sqlite_master WHERE sql NOT NULL;
I guess I didn't phrase that properly. What I have been looking
H. Wade Minter wrote:
..
Here's what I ended up with - it's not incredibly robust or portable,
but does what I need:
# Get the table schema information
my $sth = $dbh->table_info();
while ( my $row = $sth->fetchrow_hashref )
{
if (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 25 May 2004, Puneet Kishor wrote:
Do want to elaborate more? Why is the code not correct even with the
correction? We will all learn from your input. Btw, I do start with the
disclaimer that the code is untested. It is merely meant as a
Hi Randy,
On May 24, 2004, at 3:58 PM, Randy J. Ray wrote:
No, this won't work (not even with the correction, which is still not
correct code).
Do want to elaborate more? Why is the code not correct even with the
correction? We will all learn from your input. Btw, I do start with the
disclaimer
No, this won't work (not even with the correction, which is still not correct
code).
To export a database, you need more than just the contents. You need the
structure (schema), indices, constraints, etc. All of this can be created using
the DBD::SQLite driver, but you have to have the
Corrected one obvious error...
Puneet Kishor wrote:
On May 24, 2004, at 8:34 AM, H. Wade Minter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm investigating migrating my Perl/Tk application from MySQL to
SQLite. I've got most of the conversion to DBD::SQLite done, but there
are
On May 24, 2004, at 8:34 AM, H. Wade Minter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm investigating migrating my Perl/Tk application from MySQL to
SQLite. I've got most of the conversion to DBD::SQLite done, but there
are a couple of areas I'm stuck on.
My first issue is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm investigating migrating my Perl/Tk application from MySQL to SQLite.
I've got most of the conversion to DBD::SQLite done, but there are a
couple of areas I'm stuck on.
My first issue is that I need to be able to export and import database
13 matches
Mail list logo
