MySQL Dumps into SQLite

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

MySQL Dumps into SQLite

Stephen Chrzanowski
This is a dump from a MySQL table I created a few years ago.  I'm not
moving this particular database into SQLite, but, from what I learned today
about MySQL dumps and the commenting system, I was kind of interested on
how SQLite would handle the rest of the following statement:

CREATE TABLE `Clusters` (
  `ClusterID` int(11) NOT NULL auto_increment,
  `ClusterName` varchar(50) NOT NULL default '',
  `Description` text NOT NULL,
  `GroupID` int(11) NOT NULL default '0',
  `ClusterOrder` int(11) NOT NULL default '255',
  PRIMARY KEY  (`ClusterID`)
) ENGINE=InnoDB DEFAULT CHARSET=ascii;

Obviously, SQLite doesn't know what ENGINE is, or anything of the sort
(Actually, this statement didn't work due to the auto_increment keyword.
Once I removed it, I got to the meat and potatoes of this question)

The version of SQLite I'm using on this ancient machine is 3.5.9.  I cannot
upgrade it, as the OS is long out of support, isn't used by anyone other
than our staff for a jump point to other servers, and there's so much
legacy crap on this box that upgrading would break anything that is running
on it.  I know SQLite3 is mostly backwards compatible, but I'm not going to
go playing with a production machine. ;)

Could there be an inch of movement for the future so that in this
particular example, SQLite would ignore everything between that final
closing bracket and the semi-colon?  Obviously a lost cause on this
particular host, but, thinking about the future and all...

(FWIW, I just tried on 3.20.0 and the ENGINE thing is still a "broken"
thing)
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|

Re: MySQL Dumps into SQLite

J. King-3
On February 11, 2019 2:19:27 PM EST, Stephen Chrzanowski <[hidden email]> wrote:

>This is a dump from a MySQL table I created a few years ago.  I'm not
>moving this particular database into SQLite, but, from what I learned
>today
>about MySQL dumps and the commenting system, I was kind of interested
>on
>how SQLite would handle the rest of the following statement:
>
>CREATE TABLE `Clusters` (
>  `ClusterID` int(11) NOT NULL auto_increment,
>  `ClusterName` varchar(50) NOT NULL default '',
>  `Description` text NOT NULL,
>  `GroupID` int(11) NOT NULL default '0',
>  `ClusterOrder` int(11) NOT NULL default '255',
>  PRIMARY KEY  (`ClusterID`)
>) ENGINE=InnoDB DEFAULT CHARSET=ascii;
>
>Obviously, SQLite doesn't know what ENGINE is, or anything of the sort
>(Actually, this statement didn't work due to the auto_increment
>keyword.
>Once I removed it, I got to the meat and potatoes of this question)
>
>The version of SQLite I'm using on this ancient machine is 3.5.9.  I
>cannot
>upgrade it, as the OS is long out of support, isn't used by anyone
>other
>than our staff for a jump point to other servers, and there's so much
>legacy crap on this box that upgrading would break anything that is
>running
>on it.  I know SQLite3 is mostly backwards compatible, but I'm not
>going to
>go playing with a production machine. ;)
>
>Could there be an inch of movement for the future so that in this
>particular example, SQLite would ignore everything between that final
>closing bracket and the semi-colon?  Obviously a lost cause on this
>particular host, but, thinking about the future and all...
>
>(FWIW, I just tried on 3.20.0 and the ENGINE thing is still a "broken"
>thing)
>_______________________________________________
>sqlite-users mailing list
>[hidden email]
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

For what it's worth it's not possible to ignore anything after the closing bracket: SQLite itself uses this space to declare WITHOUT ROWID tables.
--
J. King
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|

Re: MySQL Dumps into SQLite

Stephen Chrzanowski
Ah yes.  I forgot about that.  I don't use WITHOUT ROWID typically, so it
didn't enter the thought process.


On Mon, Feb 11, 2019 at 2:29 PM J. King <[hidden email]> wrote:

> On February 11, 2019 2:19:27 PM EST, Stephen Chrzanowski <
> [hidden email]> wrote:
> >This is a dump from a MySQL table I created a few years ago.  I'm not
> >moving this particular database into SQLite, but, from what I learned
> >today
> >about MySQL dumps and the commenting system, I was kind of interested
> >on
> >how SQLite would handle the rest of the following statement:
> >
> >CREATE TABLE `Clusters` (
> >  `ClusterID` int(11) NOT NULL auto_increment,
> >  `ClusterName` varchar(50) NOT NULL default '',
> >  `Description` text NOT NULL,
> >  `GroupID` int(11) NOT NULL default '0',
> >  `ClusterOrder` int(11) NOT NULL default '255',
> >  PRIMARY KEY  (`ClusterID`)
> >) ENGINE=InnoDB DEFAULT CHARSET=ascii;
> >
> >Obviously, SQLite doesn't know what ENGINE is, or anything of the sort
> >(Actually, this statement didn't work due to the auto_increment
> >keyword.
> >Once I removed it, I got to the meat and potatoes of this question)
> >
> >The version of SQLite I'm using on this ancient machine is 3.5.9.  I
> >cannot
> >upgrade it, as the OS is long out of support, isn't used by anyone
> >other
> >than our staff for a jump point to other servers, and there's so much
> >legacy crap on this box that upgrading would break anything that is
> >running
> >on it.  I know SQLite3 is mostly backwards compatible, but I'm not
> >going to
> >go playing with a production machine. ;)
> >
> >Could there be an inch of movement for the future so that in this
> >particular example, SQLite would ignore everything between that final
> >closing bracket and the semi-colon?  Obviously a lost cause on this
> >particular host, but, thinking about the future and all...
> >
> >(FWIW, I just tried on 3.20.0 and the ENGINE thing is still a "broken"
> >thing)
> >_______________________________________________
> >sqlite-users mailing list
> >[hidden email]
> >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
> For what it's worth it's not possible to ignore anything after the closing
> bracket: SQLite itself uses this space to declare WITHOUT ROWID tables.
> --
> J. King
> _______________________________________________
> sqlite-users mailing list
> [hidden email]
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users