Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
All I want is 1 record and FAST (an existence check)
Yes, but it all depends on the application. Perhaps it is checking for existance before inserting, so the row is actually wanted, or maybe 99% of the time the row will exist, in which case it could still be quicker to resolve a sorry situation 1% of the time. It is just another option. -
All I want is 1 record and FAST (an existence check)
New user, so excuse the late response. If there are contraints on the table, it may actually be quicker to try to insert a row. If that row already exists, then the insert will be rejected by just accessing the index. Eric -
Odd Timestamp behaviour?
Net Express 4.0 on Windows XP Using ESQL options to establish ODBC connection to Connect DB2 which links to a remote IBM Mainframe Obtaining a timestamp. Neither mainframe format SET :x = CURRENT TIMESTAMP 0r UDB format VALUES ( CURRENT TIMESTAMP ) INTO :x work. Both result in SQLCODE -104...
