View Issue Details

IDProjectCategoryView StatusLast Update
000247110000-011: Historical AccessSpecpublic2015-07-21 16:04
ReporterNathan PocockAssigned ToRod Stein  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Target Version1.03Fixed in Version1.03 
Summary0002471: HistoryUpdate: Validation on inserting records exceeding the bounds of the database
Description

CMPWG May-9-2013:

What should a Server do if a Client attempts to insert data that:
(a) is way into the future, e.g. timestamp + 10 years.
(a) is way in the past, e.g. timestamp - 100 years.

Should the server validate and return an error? or should it blindly allow the behavior?

We would like the spec to mention this as a possibility at a minimum, and then to assert the expected result, if any. We realize that we do not want to force behavior, but we do think that some commentary on what is or should-be acceptable is needed.

We have test-cases that are attempting this behavior, but we're currently unsure of what to expect from the Server. Thanks.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Rod Stein

2015-06-04 17:55

developer   ~0006107

Fixed in 1.03 draft 03

Added text to the general section for Historical Assess specific usage of Services section.
"Vendors are free to archive data and Events in any way they choose but it is expected that archives that support inserting be able to insert into the archive at the StartOfOnlineArchive time and later (See HistoricalDataNodes 5.2). It is expected that archives that support inserting be able to insert into the archive at least 24 hours into the future. Specific limits will be vendor defined. See 6.8 for details on result codes when vendor limits are exceeded."

Ensured each Insert and Update method had text pertaining to the error code when the data or event isn't allowed. Events already had the text.

Jim Luth

2015-06-23 15:39

administrator   ~0006166

We reviewed and agreed to remove this statement:

"Vendors are free to archive data and Events in any way they choose but it is expected that archives that support inserting be able to insert into the archive at the StartOfOnlineArchive time and later (See HistoricalDataNodes 5.2). It is expected that archives that support inserting be able to insert into the archive at least 24 hours into the future. Specific limits will be vendor defined. See 6.8 for details on result codes when vendor limits are exceeded."

Issue is not closed yet pending Errata update.

Jim Luth

2015-07-21 16:04

administrator   ~0006246

Reviewed and agreed to Errata.

Issue History

Date Modified Username Field Change
2013-05-09 19:13 Nathan Pocock New Issue
2013-05-28 17:44 Jim Luth Status new => assigned
2013-05-28 17:44 Jim Luth Assigned To => Rod Stein
2014-08-19 17:37 Jim Luth Category (No Category) => Spec
2014-08-19 17:37 Jim Luth Target Version => 1.03
2015-06-04 17:55 Rod Stein Note Added: 0006107
2015-06-04 17:55 Rod Stein Status assigned => resolved
2015-06-04 17:55 Rod Stein Resolution open => fixed
2015-06-23 15:39 Jim Luth Note Added: 0006166
2015-07-21 16:04 Jim Luth Note Added: 0006246
2015-07-21 16:04 Jim Luth Status resolved => closed
2015-07-21 16:04 Jim Luth Fixed in Version => 1.03