could it be?

[Anon]

I will have a table where around 600 persons will be inserting data and i have a question

Is it posible to the 600 persons to insert diferent records at the same time, they would not never update a row just insert new ones.

[Anon]

YES THEY CAN

[[deleted]]

your caps lock key is broken.

[[deleted]]

Can you explain your problem a bit more?

[Anon]

Actually, it looks like it was working to me 😉

[[deleted]]

Did it? it didn't seem to do that on/off thing that keys normally do :-)

[Anon]

i don't know if this is a problem i was worried about the fact that there will be too many people (500 or 600)sending data to the server at the same time 'cos it's a script that registers sales to generate reports later... so i know that if i have to update a row i have to lock the table or use transactions but i didn't know if it will be posible to insert new rows at the same time...but KELKAR MANDAR with or without the caps working tells IT IS NO PROBLEM.

[[deleted]]

Well, that is not entirely true.

Yes you can add records with 600 people at the same time, but only if your database supports row-level-locking.

For example, MySQL 3.x only supports table-level-locking, which means that every time someone inserts a record, the entire table is locked and nobody else can do anything with it. That will be much too slow for you.

A few other things to remember:
- Does your database have enough memory to allow 600 concurrent connections?
- Does your database/application have good consistency control? Is it possible that several users enter the same data?

[Anon]

-Users will be saleing a certain number of products which are the same for every one so the only it has to be diferent from row to row is the user who sales a thing.
-How many memory are we talking about for 600 users?
-And yes i'm using mysql 3.x but i'm downloading mysql 4.0.1 to see if it has row level locking.......

by the way HAPPY NEW YEAR FOR EVERY ONE.

[Anon]

Hi!

While row-level locking is a good thing, you don't need it as Inserts are not dependent on it. Updates are, indeed, but inserts don't need row locking. So 600 concurrent inserts (which won't happen in any case, but who knows?) won't knock the wind out of your database server.

Hope it helped,

Happy New Year,
Stas

[[deleted]]

MySQL takes about 2 Megabytes per connection. If you reall need 600 concurrent connections, you'll need at least 600x2=1200Megabytes of memory.

btw: mysql 4.0 does have row-level-locking (finally)