I designed a java enter in which customers could be instantly placed/selected lines into/in one mysql database, but tend to not modify any existing lines, tables, db, or privilages. I acquired an internet site and located it in 1and1.com, but sadly I discovered that it is a discomfort(impossible) to possess multiple customers for just one database and also to remotly connect with a database.

I'm wondering what exactly are my options here?
I guess the first is always to get another host that enables me to get this done.
The only real other option I'm able to think about is the fact that in some way I have the ability to send from java the data to this site, and so the web site to connect with the database. (no expert in php, html, or no matter what i ahve to complete (be by embbedding a browser on my small GUI or by doing the work underneath the hood).

This really is my first attempt to produce a program that connects for an online database, so be nice.

Note: program labored in localhost.
1&1 support useless.

Just about all (web)programs which use a database, connect with the database with one database user for the entire application. Getting another database user for every user from the application is definitely an uncommon design.

So, you need to configure one database user, that the application uses to see from or email the database this database user is in addition to the customers of the application and it is shared by all customers of the application. There should not be any one-to-one mapping from application customers to database customers.

You will find different causes of this. One of these is scalability. Most databases cannot handle 1000's of connections simultaneously. For those who have an internet application that enables 1000's of concurrent customers, you won't want to possess a database reference to a distinctive username for every of individuals customers. Rather you need to make use of a connection pool having a small group of database connections the connections within the pool are used again whenever among the web application customers must perform an action that accesses the database.