if you run red hat and netscape 7.0, do not
click on the tagline "the only thing republicans need to know". its a flash that moves your netscape window around, so you can't close it. i had to ppower cycle. thanks.
i've been a emusic subscriber for 6 months now. It is a great service. They have an increadible Jazz selection. I just wanted to "me too" this one because in this case two recommendations are better than one.
Recently downloaded albumns:./JoniMitchell/WildThingsRunFast./LuckyThompson/LuckyStrikes./Miles_Davis/walkin./MongoSantamaria/GreatestHits./EddieHarris/ForBirdsAndBags./John_Coltrane/StandardColtrane-StardustSessions./Khachaturian/PianoMusic./McCoyTyner/EchosOfAFriend
thats the most recent of 40 or so i've downloaded since i joined.
dave
Thanks for the insight and the include technique. I understand that having the SQL in the JSP is ugly, conceptually, but when making a Model 1 web application, it just seems more sensible. One day i'll get my boss to give me a month to redesign our product as a Model 2 app, but til then i'm just trying to get it done.
my tag looks like this:
SELECT id, name, price from tblProduct
i can use this tag in any page,
and its displays the rowdata,
formatted by the template.
ok if the backend changes from a SQL
database to something else, i've got
problems. i see that point. but the ease
of use and timesavings involved overshadows
the unlikly chance that the system will one
day not use a DBMS. i guess i could do
something like:
fieldlist="id,name,price"
objectname="product"/>
but then if i want table joins or
sort orders or where clauses or
calculations of subtotals or
whatever, i have to redesign. it
may not be best form, but in a practical
real world sense, it seems "better".
we all know SQL, the syntax is
extremely flexible and if i really
had to change out the backend i could
right a SQL statement parser and remap
the actions to the new data store.
which i have actually done for a XML
database.
anyhow thanks for your thoughts.
dave
i have a custom tag i use in JSP pages that presents rows of objects, each with several properties that can be sorted on and searched on, and links at the end of the row to edit and delete the object. the rows come from a database. the body of the tag is a sql statement which clarifies exactly which rows and fields to get. the tag has parameters which point to the templates for the look and feel of the table and the rows. i use it over and over with no modification. it takes about 15 minutes to set up. whats the "better way"?
Slashdot Mirror
I second that. #000000 on #AAAAAA (black on light/medium grey) is easy to read and easy to look at for a long time
I second that. I buy these by the box at staples/whatever and scatter them around my house. dave
no problem, i didn't loose any data. it was funny as hell for the first ten seconds, by the way.
if you run red hat and netscape 7.0, do not click on the tagline "the only thing republicans need to know". its a flash that moves your netscape window around, so you can't close it. i had to ppower cycle. thanks.
i've been a emusic subscriber for 6 months now. It is a great service. They have an increadible Jazz selection. I just wanted to "me too" this one because in this case two recommendations are better than one. Recently downloaded albumns: ./JoniMitchell/WildThingsRunFast ./LuckyThompson/LuckyStrikes ./Miles_Davis/walkin ./MongoSantamaria/GreatestHits ./EddieHarris/ForBirdsAndBags ./John_Coltrane/StandardColtrane-StardustSessions ./Khachaturian/PianoMusic ./McCoyTyner/EchosOfAFriend
thats the most recent of 40 or so i've downloaded since i joined.
dave
Thanks for the insight and the include technique. I understand that having the SQL in the JSP is ugly, conceptually, but when making a Model 1 web application, it just seems more sensible. One day i'll get my boss to give me a month to redesign our product as a Model 2 app, but til then i'm just trying to get it done.
my tag looks like this: SELECT id, name, price from tblProduct i can use this tag in any page, and its displays the rowdata, formatted by the template. ok if the backend changes from a SQL database to something else, i've got problems. i see that point. but the ease of use and timesavings involved overshadows the unlikly chance that the system will one day not use a DBMS. i guess i could do something like: fieldlist="id,name,price" objectname="product" />
but then if i want table joins or
sort orders or where clauses or
calculations of subtotals or
whatever, i have to redesign. it
may not be best form, but in a practical
real world sense, it seems "better".
we all know SQL, the syntax is
extremely flexible and if i really
had to change out the backend i could
right a SQL statement parser and remap
the actions to the new data store.
which i have actually done for a XML
database.
anyhow thanks for your thoughts.
dave
i have a custom tag i use in JSP pages that presents rows of objects, each with several properties that can be sorted on and searched on, and links at the
end of the row to edit and delete the object.
the rows come from a database. the body of the
tag is a sql statement which clarifies exactly which rows and fields to get. the tag has parameters which point to the templates for the look and feel of the table and the rows. i use it over and over with no modification. it takes about 15 minutes to set up. whats the "better way"?