Prev: DB2 SQL16003N URSOR IDENTIFIED IN FETCH OR CLOSE STATEMENT IS NOT OPEN!!
Next: Ecko Man T-Shirt cheap wholesale
From: --CELKO-- on 26 Apr 2010 22:56
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, data types, etc. in
your schema are. If you know how, follow ISO-11179 data element naming
conventions and formatting rules. Temporal data should use ISO-8601
formats. Code should be in Standard SQL as much as possible and not
local dialect.

Sample data is also a good idea, along with clear specifications. It
is very hard to debug code when you do not let us see it. If you want
to learn how to ask a question on a Newsgroup, look at:
http://www.catb.org/~esr/faqs/smart-questions.html

But the real question is why such a pair of tables, loaded with
redundant data, exist at all!! Just make a VIEW on the larger table
to get the trimmed table for whatever reason you need it.
 | 
Pages: 1
Prev: DB2 SQL16003N URSOR IDENTIFIED IN FETCH OR CLOSE STATEMENT IS NOT OPEN!!
Next: Ecko Man T-Shirt cheap wholesale