Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I need a web-service which allows admins to insert new data and viewers to see this data-tables. Therefore at first i need a database (Mysql ?). Is a mySql db on a server the right choice? Afterwards a website should be connected to this db, where users can see specific tables and admins can add new lines into this tables. Finally this tables should be able to only show the last xy-lines of the respective table.
Use-case: I have a restaurant, and when I get orders, i want to provide a simple table where the telephone-workers can add new orders (e.g. 3x pizza salami); afterwards this table is opened with view-rights on a display in the kitchen. So the chefs can create the orders.
Which database is the optimal here?
What kind of web-service is the right and how is this connected and set up?
You can use MySQL or SQL Server. And you can use Web Pages instead of web-service.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I wanna build a web app which will store a lot of data for each user, so I've got a question, which solution is better:
create a separate database for each user
create one big database and in every table add a column with user id
?another option?
Thanks!
There is no question that creating a "big" table with a column for the user id is the way to go. SQL is optimizes to handle data in tables, not to handle zillions of tables.
Here are some reasons why:
Performance. Having a separate table for each user means that you will have lots of empty space on data pages.
Combining data across all users. Having separate tables means that your queries will be really complicated.
Maintenance. Having separate tables means that adding indexes, new columns, and so on is a nightmare.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am in need of creating a table that will get its data from a database (this is done:) ).
The users must be able to filter the table if they want to find specific rows based on the their input.
The table will have around 33 columns which not all of them will be visible, but the user can drag and drop new columns whenever he likes. and be able to filter the table using values from these columns as well.
The table will look like this and every time the user inputs something on the top of a column then the table will get filtered based on that column. also multiple filters can be placed.
Any suggestions on how to do this? is it even possible?
I would like suggest you to use http://yadcf-showcase.appspot.com/DOM_source_chosen.html jquery plugin for datatable also it works with ajax source
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Right now, I have an app where theres a sales table.
So far Ive done fine with storing the status of a sale in an ENUM column type.
(APPROVAL, WAITING, PAID, INVOICED, COMPLETED)
However the client keeps wanting to add more statuses.
So I don't want to keep changing the ENUM column.
Id prefer that I just build them a customizable system, where they can create their own flags for rows.
And then the system, creates queries on the fly, based on these flags.
What would be the best method to do this?
Maybe this is too broad a question and not best for StackOverflow?
The best method is to have a reference table for the statuses. You would store the status id in the sales table, and have a foreign key relationship to the status table.
You can then add new statuses quite easily and the rest of the system will just work. You can also rename an existing status, with equal ease.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Good day! I am fairly new in PHP and I am trying to develop a website that can retrieve and display stored information from the database. The catch is, the information that will be retrieve will be based on the selected value from the list box (the list box you can create in html).
I have one list box that contains all the names of the users and would like to display all the related information for that user on a specific table in my database.
To be completely honest, I have no idea how to do this. I can retrieve all the values from a specific table in my database and that's all I know.
Hoping someone would be patient enough to teach me how to do this or guide me if this is even possible in PHP.
Thank you in advance.
You will need to read on doing database operations using PHP with PDO.
Once you've done that, the rest will be pretty easy, you will have to learn how to work with forms with PHP,
which you can do here.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Ok, I have built a custom CRM web app for a client using PHP and MySQL. The app seems to work really well for them and so I have decided to create a commercial version open to the public.
The basic idea of it is that it takes the data captured from a website and then populates the database with that. At the moment there is simply and insert statement on the front end of the website.
The thing is, I want people to be able to sign up to the service, create an account and customise it themselves to suit their needs. My idea is that once they sign up they would be provided with a form action that submitted to their account when installed on their page.
Regarding tables in the database etc, currently there is simply a customers table as there is only one website using it. If people being to sign up and use the service, do i create a new table for every account? This might be right but it seems a bit silly to me. Or is there a better way of going about this?
Usually, it's better to add a customer_id column, and add a WHERE customer_id=12345 clause to all your MySQL queries. Having a separate table per customer is certainly possible, but it may not scale as nicely.