admin & Dalkeith, either I am going in the wrong direction, or you. I cannot explain to the app users to create queries because they are not programmers. I need to create solutions in the app by providing them the possibilities of variuos data manipulation, and, it has to be possible of just one click. They never know what is behind that "one click", but usually I explain in a few sentences like: "By clicking 'TRANSFER' button you will transfer the data from database '2022' into database '2023' ". "Please be patient while data is being transfered..." So far I see I can read tables by entering connection parametres in the begining of the project creation. Correct me if I am wrong : - I was thinking to have my database schema created (empty) = database "0000"
- I should have a separate database with only one table 'users' and appropriate fields like, username, password, databasename
- In the opening of the app, user must log in and choose database to work with.
- If the database exist = continue to work with it
- If the user must/want to create a new database = enter the database name (e.g.'2023') and the app should create the new one by copying all schema tables from database "0000"
- Next is to provide options to users to calculate results from one database (query) and insert results into another database
Now, please consider the fact that whatever operation is needed, it must be provided to the user to be possible on "one click" of a button. The users don't think about code needed under the button (they don't have to). Maybe I am wrong in some steps above because I am totally new with PHPRunner, but I have a desktop solution which is working for the past 12 years and is based on the same logic. Just one comment - if anyone wonders why separate years - '2022','2023'...some users has over 1Mil records in one table/per a year - I know we can fill the same table with data and get wanted results by querying the same table (there is a field named 'year' in it) - but, can you imagine to query that table after a couple of years with 7Mil+ records? Can you imagine to make a join (union) query between tables when eachone has several Mil records? That doesn't work well. So separating databases by fiscal years is only making all database operations faster. Getting back to the problem, can you explain me: - How to provide to user that they can create a new database by just entering the name of it? (I believe I should have connection between users and databases as well, permissions etc.on the server level)
Thank you for your patience.
|