Not as robust as I'd like - since all of the "edit", "create" doesn't work without additional coding. However, your answer got me further down the road. Thanks.
Because the SQL to generate a table, index or column list is RDMBS dependent, and if you use the generic PDO driver, the driver doesn't know which RDBMS you are using.
So don't use the generic PDO driver, use the platform driver instead.
Ah okay. I guess I was mistaken. I thought the point of the PDO was that it was an intermediary that took care of the specific differences between different RDBMSes behind the scenes. Like doing a list_indexes on a MariaDB connection would have the PDO use that RDBMS's syntax, and same for Postgres, etc.
I didn't realize that it implemented only the pieces that were common between them.
No, PDO just provides a generic interface towards PHP, it doesn't do anything with regards to platform specifics.
The mysql, dblib, sqlite and sqlsrv drivers in Fuel all utilize PDO, but have a platform specific schema and list_tables() / list_columns() implementation, to deal with this.
One more question actually. So then does the mysqli driver in Fuel utilize actual mysqli? While the mysql Fuel driver utilizes PDO, not the old mysql PHP driver?
to create scaffolding based on the ORM auth packages users table then it will create a migration in your app to create the users table that is a duplicate of the one in the auth package. So if you don't get rid of that migration, then, if you do an
Donate
