B
Brian
I'm trying to create an editing interface for a product database and
I'm still mostly in the planning stage.
The client wants an easy to update page with a table that essentially
has two columns:
Product Price
In the database these are stored in different tables and in practice
there is also user information, role information, product approval
information, category information, etc etc. So the resulting query is
done with multiple joins.
I was hoping for a layout that had the product names displayed on the
left and the corresponding prices displayed in a textbox on the right,
with an 'update' button at the bottom of the page.
I figured the best control for this was probably a datalist.
I thought that the submit event could update the dataset and then I
could update the database based on the state of the dataset row (ie if
it was modified then perform an update). Though I'm a bit stuck about
where to go with this.
Efficiency isn't as crucial here since it's the admin side of things
but still it's a consideration.
Should I be pulling the dataset with multiple tables and using the
command builder to update changes? It worried me that maybe the
tables pulled would be too large (with too many products). How large
is too large I wonder.
So I guess there are two real questions here:
Should I use a datalist for this type of multiple edit with one update
button? (I'm assuming that I'd do it without any sort of edit
template)
How do I best capture/update the changes to the database?
thanks,
Brian
I'm still mostly in the planning stage.
The client wants an easy to update page with a table that essentially
has two columns:
Product Price
In the database these are stored in different tables and in practice
there is also user information, role information, product approval
information, category information, etc etc. So the resulting query is
done with multiple joins.
I was hoping for a layout that had the product names displayed on the
left and the corresponding prices displayed in a textbox on the right,
with an 'update' button at the bottom of the page.
I figured the best control for this was probably a datalist.
I thought that the submit event could update the dataset and then I
could update the database based on the state of the dataset row (ie if
it was modified then perform an update). Though I'm a bit stuck about
where to go with this.
Efficiency isn't as crucial here since it's the admin side of things
but still it's a consideration.
Should I be pulling the dataset with multiple tables and using the
command builder to update changes? It worried me that maybe the
tables pulled would be too large (with too many products). How large
is too large I wonder.
So I guess there are two real questions here:
Should I use a datalist for this type of multiple edit with one update
button? (I'm assuming that I'd do it without any sort of edit
template)
How do I best capture/update the changes to the database?
thanks,
Brian
