Reputation: 171 Stalwart
- Active Members
- Active Posts:
- 490 (0.3 per day)
- 20-December 08
- Profile Views:
- Last Active:
- Apr 24 2013 04:53 AM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 15 Oct 2012You may think you have a great idea, that's 'very lucrative', but that doesn't mean it is. I (an anyone else worth working with) is going to need more information to see if this is the sort of project we would be interested in.
It is also very important to clarify if this is a paid job, or you are expecting us to work with nothing in return.
Posted 1 Oct 2012Because I want them to look pretty as .js
Frankly the file extension is really the last thing to worry about. I would follow Dormilich's advice!
Posted 24 Sep 2012Richard, I very little formal education in web design/development. I would suggest you speak with your advisor, and make sure that the project you have outlined would fulfil the requirements and meet the spec.
I also feel it is important to ensure that the project is something that would challenge you, and something you would enjoy.
As for the project itself, it seems like it would be pretty straight forward to do!
If you need to look over more ideas, the one and only Martyr2 has a superb thread: Martyr2'S Mega Project Ideas List!
Posted 21 Sep 2012As much as I agree with your recommendations to use the PDO or MySQLi extensions over the old MySQL API, I would still consider it a good idea to learn it. Few PHP developers will be lucky enough to avoid it altogether, at least for the foreseeable future. There is just too much code out there that uses it.
With that said, it should be learned along side PDO or MySQLi, not by itself.
The mysql_* functions are slow...
What are you basing that on? (Besides the claim in that post you linked to, which is not backed up by anything.)
From all I've seen in the last few years, all the benchmarks I've managed to find, and from what I've observed in my own code, the old MySQL extension is actually slightly (emphasis on "slightly") faster than both the MySQLi and PDO extensions. Keep in mind that all three extensions rely on the exact same client library - either MySQL's Client library or, in PHP 5.3+, PHP's own MySQL Native Driver (mysqlnd) - so the only real difference in the performance is in the implementation overhead, and how it's used. As the simplest implementation of all three, the old MySQL API wrapper would (theoretically, at least) incur the least overhead.
Also, the link you posted mentions that the need for a lot of string concatenation when using the old MySQL extension is another performance hit. Interestingly the default behavior for PDO's MySQL driver is to emulate prepared statements, meaning that it will actually construct the SQL string in much the same manner we did when using the old MySQL extension. It's just hidden behind the PDO API. (It's probably done in C, not PHP, but still. The performance difference is practically non-existent.) - Another interesting point is that this emulation tends to be faster than MySQL's own handling of prepared statements. (Although, again, with a trivially small margin.)
Don't get me wrong, though. I'm not suggesting anybody use the old MySQL extension because of this.
Apologies for not making myself clear. When I was discussing speed I was referring to development speed. I am unable to update my previous post accordingly.
As for performance of pdo vs. mysql_* vs mysqli_*, I would have to agree with you. The mysql_* functions are slightly faster, but again I have no benchmarks to prove this either way, this is based solely on my own experience.
I have always found it exceptionally difficult to find good, reliable benchmarks, and would be very interested in any you have found Atli!
As for mysql_* usage, at least where I am based, most of the web development companies I have worked with use PDO, although admittedly many of these use an MVC Framework, and those that don't use mysqli_*. I actually haven't seen any mysql_* code in a live environment for a fair old while now! Of course I would assume this would vary greatly depending on your location.
Posted 20 Sep 2012I know I keep going on, but I really cannot emphasise enough how bad using the mysql_* functions is.
If you need to create a user system, that's great, but a two minute Google search found me this: Simple Login System / PDO - I haven't watched it, but if it is using PDO, I can all but guarantee it is better than your book .
- Member Title:
- D.I.C Regular
- 22 years old
- February 22, 1991
- Salisbury, Wiltshire
- Web Development
- Full Name:
- Tom Green
- Programming Languages:
- PHP/MySQL, HTML/CSS, ASP
- Website URL: