Forums Register Login

How to select columns of a table dynamically?

+Pie Number of slices to send: Send
Hi !
I am new to coding.I got a requirement where the user could see the columns available in the table. And then he selects only few of the columns to see the data.
So I am planning to put a check box to every column so whatever the columns selected by the user we can identify.But the problem is how can I write a query after taking the database connection
for dynamic selection of columns?

Please suggest me the ways to do this.

Thanks in advance.

+Pie Number of slices to send: Send
If performance is not a consideration, you can choose to get all the data anyway and filter what to show to the user based on their selection criteria.
+Pie Number of slices to send: Send
The above seems to be a valid suggestion. Else you will have to dynamically fire a query for every set of selections, which could cause a performance issue.
+Pie Number of slices to send: Send

Selecting all coulmn values can be an overhead .What is the problem in creating the SQL dynamically eg. if you are a web developer you can create a check box with column name as name of check box and create dynamic sql in java script and pass it to you java backend?
+Pie Number of slices to send: Send
Will that not fire a connection to the database, each time the selection of columns are changed? I believe that would be an overhead.
+Pie Number of slices to send: Send
It will create a connection But if you load the entire data the page loading will be very slow and It is ok to create a connection if you are closing it after use.
And there is no way we can get the data with out a connection.
+Pie Number of slices to send: Send
Again I think the approach is well determined by the size of the returned dataset.The tradeoff would be better judged then.
2
+Pie Number of slices to send: Send
Worrying about overhead before it's known that there's something to worry about is called premature optimization and should be avoided. Do what makes the most sense, and then, and only then, if there's a performance issues, address it.
+Pie Number of slices to send: Send

@Bear Bibeault .IS it a Pre mature optimization really?

Sorry if i dint ask the size of the application here..

It is well known that selecting 100 column is much slower than selecting 10 cloumns.So Is it not good to think usr will not need all columns always?

I am not questioning you ..problem here is about the design of the application...

Thinking all possible overhead (at least expected ones)is also a good way of design i believe.

Is above not true?
+Pie Number of slices to send: Send
 

Bear Bibeault wrote:Worrying about overhead before it's known that there's something to worry about is called premature optimization and should be avoided. Do what makes the most sense, and then, and only then, if there's a performance issues, address it.



Very true.

It is well known that selecting 100 column is much slower than selecting 10 cloumns



We are talking about hypothetical numbers here. Do we really know that the OP is dealing with such numbers ? It is always easier to choose the simplest solution and then chisel away at it if necessary.
It's exactly the same and completely different as this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 1234 times.
Similar Threads
Adding grids in MapBacked form
Highlighting a row in a table
JTable
search functionality with 6 inputs(oracle based)
Left most column locking
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 09:36:49.