Recommend this page to a friend! | Stumble It! | Bookmark in del.icio.us |
All requests | > | Good and simple MySQL wrapper | > | Request new recommendation | > | Featured requests | > | No recommendations | ||
by Y D - 1 year ago (2014-10-27) mysql wrapper
+4 | I'm looking for a good simple to use MySQL wrapper. There are many here. From your experience what should I go with? |
+2 | by Giovanni Ramos 35 - 1 year ago (2014-10-28) Comment Try this class which uses the power of the PDO, which offers support for MySQL and PostgreSQL, and most other popular dbs. It may be useful to you in terms of portability. |
+2 | by marcelo entraigas 35 - 1 year ago (2014-10-28) Comment Hello, I wrote a a package with that in mind. Hope you find it useful. |
+1 | by amani 65 - 1 year ago (2014-10-28) Comment This class can update all MySQL database table records. It can retrieve the list of tables of a given MySQL database and generate a HTML form to let the user choose the tables and fields he wants to update. The class takes the submitted form values and executes a SQL UPDATE query to change the table field specified by the user. With this class you can use a good interface to update and change table fields values very fast and easy via ajax. In this class you have some option to choose table records with theme value very simple. |
+2 | by Manuel Lemos 11100 - 1 year ago (2014-10-27) Comment I have been using this package to access databases for many years. It can work to access MySQL and other databases that you do not need, but provides also other interesting features. For instance it can install the schema of the database tables from a file that describes the tables. Then if you need to change the tables, for instance adding, removing, renaming tables, fields or indexes, just change the definition of the schema in the same file and tell Metabase to upgrade your schema. It is very safe, as it will tell you in advance if you want to perform a database schema change that is not supported, it will tell you in advance so it does not perform part of the changes and leave your database schema inconsistent. Putting the database schema definition on a description file is also useful to keep your database changes under your GIT or other version control system that you use. |
Recommend package | |
|