Examples of cascading.lingual.type.SQLDateCoercibleType

cascading.lingual.type.SQLDateCoercibleType

Handles conversion to and from the DATA data type in SQL. Since the DATE type is defined as not having a timezone and having only yyyy-mm-dd precision we truncate rather than convert to preserve the symmetry of conversion. The dates "2013-03-05 09:04:57 GMT" and "2013-03-05 04:04:57 -0700" are considered identical DATE values even though they represent different actual calender times. This is in line with the convention that many databases have of allowing an implicit conversion of DATE to TIMESTAMP and setting it to "yyyy-mm-dd 00:00:00" of their set default timezone.

Symmetry is not guaranteed across Lingual jobs running in JVMs set to different timezones. Set UTC time on all servers or use the TIMESTAMP datatype and {@link SQLDateTimeCoercibleType} since those are defined to represent a more precise time.

        return isNullable ? Boolean.class : boolean.class;
      case BINARY:
      case VARBINARY:
        return ByteString.class;
      case DATE:
        return new SQLDateCoercibleType();
      case TIME:
        return new SQLTimeCoercibleType();
      case TIMESTAMP:
        return new SQLTimestampCoercibleType();
      }

    }


  @Test
  public void testIntoSelectValuesDate() throws Exception
    {
    setResultsTo( "TEST", "RESULTS", new Fields( "DATE", "TIME", "DATETIME" ).applyTypes( new SQLDateCoercibleType(), new SQLTimeCoercibleType(), new SQLTimestampCoercibleType() ) );


    assertUpdate( 1, "insert into test.results values (DATE '2013-07-07', TIME '15:15:01.01', TIMESTAMP '2013-07-07 15:15:01.01')" );
    }

Examples of cascading.lingual.type.SQLDateCoercibleType

Related Classes of cascading.lingual.type.SQLDateCoercibleType