![]() |
table A(col1)
05 Mar 2014
| 4 comments
,
|
![]() |
Hi,
13 Feb 2014
| 1 comment
,
|
![]() |
Hi Guys,
11 Feb 2014
| 10 comments
,
|
![]() |
I am trying to load a small SAS table into Teradata via SAS/ACCESS connectivity & OLE DB.
28 Jan 2014
,
|
![]() |
|
![]() |
Our Teradata instances are used as a DW for our DB2 mainframe application. In those DW tables, NULL values for date fields are instead represented by '1111-11-11'. I figure this was either done intentionally as part of the design (either mainframe or DW-side) or it was out of necessity due to NULL not being allowed in a DATE field.
13 Nov 2013
| 2 comments
,
|
![]() |
Dear All
28 Sep 2012
| 2 comments
,
|
![]() |
Hello, In this case: CREATE TABLE t1 (geom ST_GEOMETRY, id PRIMARY KEY not null integer) ; CREATE TRIGGER t_ins AFTER INSERT ON t INSERT INTO t (geom, id) VALUES (null,1); I have the error : The owner expression of the UDM invocation 'ST_ENVELOPE' is not a UDT
12 Apr 2011
| 2 comments
,
|
![]() |
After reading that "The system always compresses nulls whether you specify null compression or not." in the Database Design (Sept 2007) documentation I decided to test this.
10 Mar 2011
| 4 comments
,
|
![]() |
Hello experts!! I need help in handling null and empty values in 3 (data type) scenarios. Here is what I am doing currently and I want to know if I am missing something? Is this the right way to handle it?
22 Nov 2010
| 3 comments
,
|
![]() |
Hello! I've a problem when inserting null value to TIMESTAMP column. I use arrays of parameters and insert two rows with one statement. I receive error when executing statement: "Invalid timestamp". Problem occurs only when one row has value and other is null. If two has value or are null, then problem doesn't occur. There is no problems in similar situation with another data types (e.g. VARCHAR, INTEGER). Here is my code (without error handling etc.):
07 Aug 2009
| 5 comments
,
|