Re: MYSQL WTF
| From: | Levi Morrison | Date: | Wed, 27 Jun 2012 18:05:43 +0000 |
| Subject: | Re: MYSQL WTF | ||
| References: | 1 2 3 4 5 6 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-13801@lists.php.net to get a copy of this message | ||
Mr. Efficacious,
You are incorrect, sir; you do not have to use the PHP Database Object
(PDO). The MySQLi API is up-to-date and is nearly identical to using
the MySQL functions. You don't even have to use it as an object. You
can use MySQLi with procedural style.
Levi Morrison
On Wed, Jun 27, 2012 at 11:57 AM, efficacious <efahkshish@gmail.com> wrote:
>
> Your missing the point... why would I even bother? Why would I bother updating my database
> object if the only way I could do that is by updating using the PHP database object? What is the
> point of that?
>
>
> On 6/27/2012 1:55 PM, Levi Morrison wrote:
>
> Mr. Efficacious,
>
> You are over-reacting. The MySQLi API is nearly identical to the MySQL functions, but is
> up-to-date. You can move to the procedural MySQLi with almost *NO* effort at all. Even with
> thousands of lines of code, you should be able to update everything in less than one day.
>
> Levi Morrison
>
> On Wed, Jun 27, 2012 at 11:36 AM, efficacious <efahkshish@gmail.com> wrote:
>>
>> Also why the fuck would I continue to use PHP if your going to take everything object
>> oriented? Why wouldn't I just move to a lower level language like oh idk C++ or even better
>> just C# that has been OO since they began. Why even bother with PHP at all anymore if it is going to
>> be just like every other fucking language.. PHP was a great language to use because you could build
>> anything you wanted out of small functions that did minimal.. now instead of being about building
>> your own shit and your own objects its about using the pre-built objects. Might as well just make
>> PHP a fucking APP and have everybody use that. Ridiculous. I hate you guys so much right now it is
>> not even funny. I spent 6 years teaching myself code and now when I finally am able to put it to
>> use, you guys come in and just fuck it all up.
>> I don't think you even realize the amount of damage you have done. Everything I have
>> been doing for the past 7 years is wiped to being worthless. I truly believe I am finished with PHP
>> forever.
>>
>>
>> On 6/27/2012 1:24 PM, efficacious wrote:
>>
>> Yea but if thats the case why not just update the current functions to support the new
>> features of MySQL. Now I am supposed to go back through my object and use object code to write it?
>> Please please, you tell me at what point it sounds like a good idea to create a database object from
>> a database object?
>>
>> On 6/27/2012 11:55 AM, Levi Morrison wrote:
>>
>> On Wed, Jun 27, 2012 at 12:17 AM, efficacious <efahkshish@gmail.com> wrote:
>>>
>>> To whom it may concern:
>>>
>>> How are you just going to get rid of all of the mysql functions.. I literally just
>>> finished writing 1000s of lines of code for a custom Database access object and now its all for
>>> nothing because you guys want to press your own object onto us? That is pure bullshit. This very
>>> well might be the broken straw that leads me directly opposite directions with PHP and I will do
>>> everything I can to get others to do the same.
>>> Are you guys making a programming language or a web application for fuck sake. God damn
>>> it this pisses me off to no end, all my work is worthless now... fucking year or more down the
>>> drain. Fuck you guys, eat shit and die..
>>>
>>> ~xsupporter
>>>
>>> --
>>> PHP Webmaster List Mailing List (http://www.php.net/)
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>
>> They won't be removed for quite some time; rather we've just started actively
>> telling people to stop telling them. They will probably be deprecated but not removed in the next
>> version of PHP. You will have time to upgrade. Or, if you choose, you could not upgrade your PHP
>> version. We haven't made you do anything. Regardless of what you think, the functions are
>> quite outdated, have security problems, and do not support several MySQL versions that have been
>> around for years.
>
>
>
>