Reputation: 0 Apprentice
- New Members
- Active Posts:
- 8 (0.02 per day)
- 27-August 12
- Profile Views:
- Last Active:
- Sep 12 2012 05:04 PM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Who Cares
- Your Car:
- Dream Kudos:
Posts I've Made
Posted 12 Sep 2012Wow, thanks a lot. I'm glad you posted this as this was kind of the direction that I was thinking I would have to go with it, only I wasn't sure of some of those specifics, and you had clarified at least two of the issues that I was wondering about. It's almost like you knew my next step. That is, of course, if I choose to try to support other databases; which might be a better idea to try after I've got a complete working version using mysql. Especially as it is the only one I feel like I'm relatively competent with, at the moment.
Thanks a mil, Atli. I think this is going to go into my bookmarks for a little while as I build up enough momentum with PDO to take on the task of database cross-compatibility.
Posted 11 Sep 2012Don't be one of those guys keeping crappy legacy code going long past its expire date.
Thanks for the advice, I definitely don't want to be a part of holding php back. I gave that a bit of thought, too. I don't want to be one of 'those guys' in a community where I'm still trying to be one of 'you guys'. Hopefully soon I'll putting forth some meaningful stuff and giving something back.
Posted 11 Sep 2012Thanks a lot Atli!
I've taken to heart your meaningful response to my question and have started using PDO in my project. Luckily, the way that I have organized the structure of the application has been to segregate almost all of the functional elements of it into their own directories which contain their own specific classes and files so that in future revisions I could simply replace an appropriate directory with an updated version when I felt necessary and have no effect of the other portions of the site/app. Thus allowing me to rewrite an entire section of the application without having to adapt the rest of the application to fit it in. I'm finding out that a little bit of forethought is a fine gift to give yourself when something like this arises.
PDO was developed as a unified API for all databases, not only MySQL. It allows you to use the same exact classes and methods to interact with all the databases it supports. This will save time later, if/when you start using other database systems, as you won't have to learn an entirely new API to interact with it.
One of the reasons that I had thought to go ahead with implementing PDO in my current project is because I not only want to offer it as an actual website, but also to provide a version of it that could be downloaded and installed on other's servers if they chose to host their own instead of using my site. I figured that since PDO supported so many different databases that it would be absolutely fantastic if my code could support all those other databases, as well. Man, that would have really made me feel like a badass. But, something I've been running into a lot is that there still seems to be a lot of inconsistencies with PDO's mysql support and it's support for other databases. Just one example, PDO::lastInsertId seems to have a lot of variances in it's use depending on which sql server it will be interacting with. So, in order for me to prepare the application to be used with postgresql and mssql I will have to come up with some way to safely check for server version, possibly in the pdo connection string and use some ifelse statements of try/catch blocks when using this function, which I do almost frequently. I am wondering if you happen to know of any workarounds to having to do something like this or if you know of any links that outline discussions of how other programmer's may be are dealing with these kinds of issues with PDO?
Irregardless, I'm going to stick it out with PDO. I have faith that the PHP community will work out some kind of patch to be applied to those cross-database issues in the future.
Thanks a lot for your meaningful input. It is greatly appreciated!
Posted 27 Aug 2012looks like they had to be playing around and learning. I hope.lol. This is some funny content shit, though..
Posted 27 Aug 2012Thanks. I'll have to look into mysqli a bit more. I've been having such a hard time using PDO in my php classes. But, from what I've been reading that is not too uncommon.
- Member Title:
- New D.I.C Head
- Age Unknown
- Birthday Unknown
- Years Programming:
- Programming Languages: