table A(col1)
1
2
3
5
 
table B(col2)
2
3
4
6
SQL: SEL a.* FROM tableA a left join tableB b On a,col1=b.col1 Where a.col1<5 and b.col1<5
ANSWER : 2
                  3
Who can tell me why?
 
 

Hi,
I am exporting a large amount of data into a file.The specification is like each column should be seperated by pipe.If there is no data,there should be space.(| |)
I need file in this format
if there is data it should be like this

Hi Guys,
In the case statement if i give it as mentioned below:
where col1=(case when :col1='xyz' then 'xyz' else NULL end)

I am trying to load a small SAS table into Teradata via SAS/ACCESS connectivity  & OLE DB.
The table is mostly NULL and consists of: id, SiteA, SiteB, SiteC, SiteD.  The Site variables are populated with "Yes", "No", or SAS NULL ''.  Only one column is populated at any time.  Therefore the data looks as follows: 

Hello,

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.

Dear All
I have stored information about company sales in a table tab_sales as follows:
Company Week         Date                 Sales
Co. 1        201237      10-09-12           $200
Co. 1        201237      12-09-12           $150
Co. 1        201237      14-09-12           $420

Hello,

In this case:

CREATE TABLE t1 (geom ST_GEOMETRY, id PRIMARY KEY not null integer) ;
CREATE TABLE t2 (geom ST_GEOMETRY, id PRIMARY KEY not null integer) ;

CREATE TRIGGER t_ins AFTER INSERT ON t
REFERENCING NEW TABLE AS nt
FOR EACH STATEMENT
BEGIN ATOMIC (
INSERT INTO t2 SELECT geom.ST_Envelope(), id FROM nt WHERE geom IS NOT null;
)
END;

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
What does it mean ?
Why ST_ENVELOPE is executed ?
And how to solve it ?

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.

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?

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.):


SQLSetStmtAttr(hstmt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER)2, 0);