I also accidently posted this in Jakarta/Tomcat.
What would be a recommended approach to storing form data?
I have a long form that will require several pages, so I cannot put this all in one page. What would be the most effecient method of store the information from each page?
Thanks!
Thanks sedj! I did not know I could actually do that, i wasn't sure if it was tomcat specific code. As you can tell, i'm new to jsp/java,tomcat.
Thanks!
JE
I would like to update TABLE_A using TABLE_A.
Something like this...
UPDATE TABLE_A
(FLD_START)
=
(
SELECT fld_A from tbl_ref where tbl_ref.fieldB = table_a.fieldB from TABLE_A)
but i get a "too rows returned" error..
Any ideas or guidance?
Thanks
JE
I have 180 partitions; not configured for transportable tablespaces.
Each partition is huge, (approx 10 million rows) per partition.
I am moving this data to another database (same table name, but different tablespaces names).
What would be the most efficient way of copying the data over...
If I do not have striping, should I create a tablespace for INDEX and DATA each? and ensure that these get put on different disks? This is for an OLTP system. Should an INDEX and DATA tablesapce be created for each table?
SQL> SELECT TNAME FROM TAB WHERE TNAME LIKE 'TEST_%';
TNAME
------------------------------
TEST2
TESTA
TESTB
TESTING123
TESTINGA
TESTJE
TEST_12_JE
TEST_13_JE
TEST_PROCESSES
TEST_TAB
This is pulling all of these..i only want it to pull the following:
TEST_12_JE
TEST_13_JE
TEST_PROCESSES...
Is there a way to interpret exceptions? For example, if I want an ORA-00001 to display a message?
if(e=="ORA-00001")
{
out.println("Constraint violation!");
}
How can i insert data randomly from another table?
TBL_A
-----
ID
NAME
TBL_A has several records (lets say 10). I want to use the "ID" from this table and insert into another table along with other data. Any ideas? Thank!
DECLARE
BEGIN
FOR i IN 1..200 LOOP
INSERT into TBL_B values...
I have a checklist form that has 44 questions? A simple 1 or 0 is collected.
My question is, should I create a wide table with 44 fields, plus an additional two fields that identify the user and form, or should I have a "user/form" table and then a "detailed" table with a "user/form" key that...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.