Hi,
Basically my job is to develop web applications using a database as backend. What I have been doing till now is,
Basded on the requirement of the client,
- I draw a basic sketch of what the tables are ,how they look like
- fields in those tables and some one-to-one or many-to-one or many-to-many relations
Although I am not perfect at these things, I try to figure out how the relations should be from my past projects that I worked on. But there are still some doubts about this in my mind.
If the client asks that he wants a particular data, I try to achieve it either through a direct SQL
query or thought the scritp (in most cases PHP), if I am unable to figure out a query at all for that particular request.
Now, here comes my question.
Based on the relationships that I figured out while developing tables, are there any limitations to what a client can ask? What I mean to say by this is, the client will ask that he wants list all the indidual products, their counts, associated category, all the counts of
category, the products in each category and the their prices, sum of all the category prices and the total prices so on so forth.
This is just an example of one request to explain my situation.
Now, if there is any request that can potentially take longer time for the exection, can the developer satisfy this request by breaking down the request? Do I need to tell him why is this break down necessary? What if he feels that I am not capable of doing it in a single shot?
Is every report that he asks for need to be in single query? or will there be any need to itake the help of PHP to proces one loop and based on the values that I get, I put some conditions to apply rules that the client wants?
What is the better way to do this kind of job?
Any views?
Thanks.