Should I Use Pear with PHP?

[dealmaker]

Hi,
I am using php and mysql. I want to ask you guys' opinion about PEAR. One of its feature is PEAR:DB. Should I use it? I am not sure if I will change DB in the future, no one knows. But I will keep using mysql as my database until I think that it can't handle something in the future. I also heard that PEAR is slow.

What do you think?
Many thanks.

[Digger3000]

Is "PEAR" a database?

[dealmaker]

No, PEAR is a extension package for php.

Is "PEAR" a database?

[Kurashu]

MySQL is a database. PEAR is an extension pack.

Two COMPLETELY different pieces of software. NOW, if you are asking if you should use the built-in MySQL functions over the PEAR db class the main question to ask is "Will I be switching databases?" If the answer is yes or more than likely, then go with PEAR. other wise no unless you plan on developing a script aimmed at PEAR users.

[Digger3000]

No, PEAR is a extension package for php.
I thought so.

[dealmaker]

What happens if I am not sure whether I will change db from mysql to something. I think the reason is that I am not sure how scaleable mysql is. Can mysql handle heavy traffic? If not, I may need to change db in the future.

How hard is it to change db anyway if not using PEAR? Just need to change the query functions, index, and optimizations?

MySQL is a database. PEAR is an extension pack.

Two COMPLETELY different pieces of software. NOW, if you are asking if you should use the built-in MySQL functions over the PEAR db class the main question to ask is "Will I be switching databases?" If the answer is yes or more than likely, then go with PEAR. other wise no unless you plan on developing a script aimmed at PEAR users.

[Kurashu]

MySQL is pretty good at heavy traffic from what I hear and you should be safe with it as long as you have a good database design. If you do encounter trouble, rethink your DB design and if you still have trouble I reccomend switching to PostGreSQL.

As for hard it is, it is how hard you make it.