[
https://issues.apache.org/jira/browse/DERBY-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5974:
---------------------------------
Description:
After we implement TIMESTAMP WITH TIMEZONE, we should consider converting our
existing TIMESTAMP metadata columns to be TIMESTAMP WITH TIMEZONE. This may
insulate us from the hiccups around shifts between winter and summer time as
seen, for instance, on DERBY-5966.
The current TIMESTAMP metadata columns are:
SYSSTATEMENTS.LASTCOMPILED
SYSSTATISTICS.CREATIONTIMESTAMP
SYSTRIGGERS.CREATIONTIMESTAMP
SYSUSERS.LASTMODIFIED
as seen by running the following script (which uses the DBMDWrapper routines
attached to DERBY-3973):
connect 'jdbc:derby:memory:db;create=true';
create procedure registerPublicStaticMethods( in connectionURL varchar( 200 ),
in printSQL boolean )
language java parameter style java modifies sql data
external name 'DBMDWrapper.registerPublicStaticMethods';
call registerPublicStaticMethods( 'jdbc:default:connection', false );
select table_name || '.' || column_name
from table ( getColumns( null, null, '%', '%' ) ) s
where data_type = 93;
was:
After we implement TIMESTAMP WITH TIMEZONE, we should consider converting our
existing TIMESTAMP metadata columns to be TIMESTAMP WITH TIMEZONE. This may
insulate us from the hiccups around shifts between winter and summer time as
seen, for instance, on DERBY-5966.
The current TIMEZONE metadata columns are:
SYSSTATEMENTS.LASTCOMPILED
SYSSTATISTICS.CREATIONTIMESTAMP
SYSTRIGGERS.CREATIONTIMESTAMP
SYSUSERS.LASTMODIFIED
as seen by running the following script (which uses the DBMDWrapper routines
attached to DERBY-3973):
connect 'jdbc:derby:memory:db;create=true';
create procedure registerPublicStaticMethods( in connectionURL varchar( 200 ),
in printSQL boolean )
language java parameter style java modifies sql data
external name 'DBMDWrapper.registerPublicStaticMethods';
call registerPublicStaticMethods( 'jdbc:default:connection', false );
select table_name || '.' || column_name
from table ( getColumns( null, null, '%', '%' ) ) s
where data_type = 93;
> Convert TIMESTAMP metadata columns to TIMESTAMP WITH TIMEZONE after we
> implement that datatype.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-5974
> URL: https://issues.apache.org/jira/browse/DERBY-5974
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
>
> After we implement TIMESTAMP WITH TIMEZONE, we should consider converting our
> existing TIMESTAMP metadata columns to be TIMESTAMP WITH TIMEZONE. This may
> insulate us from the hiccups around shifts between winter and summer time as
> seen, for instance, on DERBY-5966.
> The current TIMESTAMP metadata columns are:
> SYSSTATEMENTS.LASTCOMPILED
>
> SYSSTATISTICS.CREATIONTIMESTAMP
>
> SYSTRIGGERS.CREATIONTIMESTAMP
>
> SYSUSERS.LASTMODIFIED
>
> as seen by running the following script (which uses the DBMDWrapper routines
> attached to DERBY-3973):
> connect 'jdbc:derby:memory:db;create=true';
> create procedure registerPublicStaticMethods( in connectionURL varchar( 200
> ), in printSQL boolean )
> language java parameter style java modifies sql data
> external name 'DBMDWrapper.registerPublicStaticMethods';
> call registerPublicStaticMethods( 'jdbc:default:connection', false );
> select table_name || '.' || column_name
> from table ( getColumns( null, null, '%', '%' ) ) s
> where data_type = 93;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
