[Maxips2]

Quote:

Originally Posted by Jay_ It depends on the circumstances - I can think of a few scenarios in the past where I have wanted to port my SQLite database to MySQL purely for communication purposes. SQLite is a local embedded database engine, and as the name suggests it's only "lite" - that means complex tables packing loads and loads of data consisting of many advanced queries don't really meet the database engines goal as it's not designed for large scale production environments. Although technically it can be embedded too, MySQL generally is standalone. This makes communication with a MySQL database from an external source much easier. It also has performance tuning features and can normally handle large amounts of data much better.

There is a point in what you are saying.
But I think that if you already chose to use a database then you would probably know which one suits for your needs.

If you are planning on using more complex queries and you need better performance or communicate your database from another source, then you should probably aim for MySQL at first place and not SQLite.

Besides that, I still think that porting from SQLite to MySQL, even with this plugin isn't going to be that easy, and will actually make it slightly harder for users who are used to the common syntax of MySQL functions (StrickenKid's and BlueG's MySQL plugin).

That is just my opinion of course.