PHP Databasing

[The-Last-Escape]

I have learnt a few new things about databasing but I had some questions.

I have heard at www.w3schools.com that ms access was a database that should only used for small type databases, I have though talked to a few sql exprts, and they said they use data for everything, even huge massive databases with thousands and thousands of entrys.  If there is a reason to not use msaccess for major databases what would those reasons be.  And if I need another program for major databases, what is a good database program, that I can use that supports mysql, dbqwik, postgresql, and others as well, that is a best database program that is fairly easy to use, and can be used for all purposes big and small.  I sort of want something that can work with all forms of database I want to use mysql with php, but I still want to know dbqwik, postgresql, and the other's out there in case if a client needs something done, or wants somethng done with a specific database type, or incase if the server I am working on, only supports a certain type.

[trq]

what is a good database program, that I can use that supports mysql, dbqwik, postgresql, and others as wel

 

MySql and Postgres ARE database servers. You seem a little confused.

 

The reason w3schools.com talk about access it it is primarely an asp site. And allot of asp begginers use access for its ease of use. It is a desktop database application, not really designed for large databases.

 

SQL itself is a language used to query data in databases. So, once you learn one db, all others are much these same. Some of course do have certain features which others don't but SQL itslef is a Standard.

[The-Last-Escape]

Thank's

[veridicus]

Thousands of records in not a massive database, but a small one.  MS Access completely chokes when a table has hundreds of thousands of records (in my experience > 200,000 and it's unusable).  MS Access also can't handle multiple connections well.  It's meant as a desktop database for very few users, not backend.  Anyone who says Access is good for a "real" web app doesn't know what they're talking about (unless they have 5 users).

 

mysql isn't the greatest, but it can handle medium sized databases relatively well.  It's best for situations where your app has many small queries, even on large datasets.  It becomes troublesome when you need very complex queries.

 

I'm speaking from a lot of experience with both databases.

 

Pick the database that best fits each situation.  But I think what your asking about is a front-end to work with each database.  I've used a few but always end up back at the command line.  The GUI tools are just too limiting for me.