|
|
Posted by dorayme on 08/22/07 01:18
In article <Xns9993D45563043BootNic@216.168.3.70>,
BootNic <BootNic@bounce.earthlink.net> wrote:
> > <http://bootnic.atwebpages.com/DataRowSelectExample.php?row=1#j-kl
> > o70001>
> >
> > I notice that to get a different row I need to change both the
> > "row=..." and of course, the end number 7000... in the url bar.
> > This does the trick of directing a complete outsider to the table
> > with a particular row highlighted. This might well do me! Thanks
> > for this. I am almost sure to use it. Will let you know how it
> > goes.
>
> If you are pulling this out of a data base perhaps the id and row should
> be based on the uniqueId, and not the row count as in my very simple
> example. Same basic ideal, just matching it to something a bit more
> dependable.
I left out of my previous message some queries about this matter.
Just thought I would first look at your script more closely.
Ideally, I would like to id each row <tr id="..."> because it
would be nice not to have to ask my client to put text with
row="..." in as part of their code. It is desirable to make the
code for the product exactly the same as this id. I have nothing
to do with my client's database. I just want to make sure that
they have a unique address for each product in my table, there is
one product per row and each row can have an id. This way there
is a simple rule for the client to make a unique url for any
product whatsoever, namely:
Put # followed by the code onto a base url.
Whereas with your scheme, I have to tell them the exact appendage
for each product, or they have to look to see the row it is on
(There are other categorization issues I have left out for
simplicity, the rows will be broken up and there will probably
end up being more than one table).
So, I will have to look at this more closely.
--
dorayme
Navigation:
[Reply to this message]
|