I've been coding for over 20 years now! (WOAH, do I feel old)
I've touched just about every resource imaginable under the Sun (too bad they were bought out by Oracle)
I'm the creator and maintainer of the PUDL (PHP Universal Database Library) project. The main goal is to create a single, simple, standard interface for interacting with ANY SQL implementation supported by PHP. Existing tools like PDO fall way to short in this regard, and have an awkward learning curve (DSNs get confusing for new developers). Beyond just a basic "hey, lets execute a SQL query" mentality, this library is actually more focused on generating the query itself based on what the current database engine is. This way, it truly is just a single-line configuration option to switch between database engines.
Personally, I work almost exclusively with MariaDB (MySQL fork) these days, and mostly in a Galera clustering environment. I don't have a large enough deployment of Microsoft SQL Server or PostegreSQL Server to test more unique oddities and edge cases with these systems. I'm currently also implementing a SQLite database for a production system, so that is at least covered!
The other big area is working on detailed documentation for each and individual method in the library. I'm not much of a technical writing, but trying my best! I'm always open to suggestions on how to make the docs the best they possibly can be to on-board new developers interested in interacting with SQL databases.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
WELL, now that GitHub seems to be back to normal, here is a link to my project!
github.com/darkain/pudl
I'm the creator and maintainer of the PUDL (PHP Universal Database Library) project. The main goal is to create a single, simple, standard interface for interacting with ANY SQL implementation supported by PHP. Existing tools like PDO fall way to short in this regard, and have an awkward learning curve (DSNs get confusing for new developers). Beyond just a basic "hey, lets execute a SQL query" mentality, this library is actually more focused on generating the query itself based on what the current database engine is. This way, it truly is just a single-line configuration option to switch between database engines.
Personally, I work almost exclusively with MariaDB (MySQL fork) these days, and mostly in a Galera clustering environment. I don't have a large enough deployment of Microsoft SQL Server or PostegreSQL Server to test more unique oddities and edge cases with these systems. I'm currently also implementing a SQLite database for a production system, so that is at least covered!
The other big area is working on detailed documentation for each and individual method in the library. I'm not much of a technical writing, but trying my best! I'm always open to suggestions on how to make the docs the best they possibly can be to on-board new developers interested in interacting with SQL databases.