Re: php/mySQL capabilities

Several hundred tables? It sounds like one for each customer? Well, it's undoubtedly very poor database design, but go ahead and knock yourself out. PHP/MySQL can more than handle what you're looking for. At least as far as you've already described. What you haven't described, however, is hopefully the bulk of the usefulness of your imagined system. Folks tend to put things in RDBMSs not because of update frequency and not because of the simple fact that their runtime platform allows them to connect to one, but because of the advanced built-in searching & sorting capabilities and data integrity features of an RDBMS. On a cautionary note, though: before pitching this project to your boss/friends/investors/grandma/whatever, you might want to research a bit on relational database design. Specifically look at "views" and "triggers," which will probably allow you to use a properly designed database schema and help protect your users' information from being updated by unauthorized folks. If you do decide to go with a properly designed database and will be using views and triggers, you might want to check out Interbase or PostgreSQL because they support views and triggers. What are you doing still reading this? Get thee to a bookstore or on to Google and start studying up on this stuff! Doug Paul Caheny was heard at 11:53 PM 8/8/00 -0400 to say: >Hi all, > >I am a newcomer to php/mySQL but really like what I have seen so far. I am >interested in working on a project which requires a web based db. I am just >wondering if php/MySQL would be suitable for my requirements. > >The DB is going to contain several hundred seperate tables, and certain >records must be updateable by certain people (with unique password) only. >There will be about 200 - 300 seperate account holders on the DB each one >needs to be able to update their and only their information stored in the DB >from their own offices around the country (Ireland) over the web. Although >the frequency of updates would be low, say 1 update per account per week, >i.e. 200-300 updates per week. I am just wondering if php/mySQL can handle >these sort of requirements - updates from multiple locations over the web >and the whole idea of each account holder only being able to update >information pertaining to themselves in the DB. > > >Thanks in advance, any advice would be greatly appreciated, > >Paul Caheny.