<?xml version="1.0" encoding="UTF-8"?>
<tickets type="array">
<ticket>
  <assigned-to-id>apFgCgqb4r3Q6XeJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-06-01T04:55:18-07:00</created-on>
  <description>Existing Details &#8211; Make sure the existing details are complete and correct:

* Documentation - Go through the IndexedTable class and document all objects and code bodies according to the conventions outlined in the EsiObjects Coding Conventions document.

* Regression Test - Before expanding the functionality of IndexedTable, expand (rewrite) the regression test for the IndexedTable in the RegressionTest library.

* Base 1 or 0 &#8211;  Make sure the use of base 0 (internal) and 1 (external) is consistent and well documented.

* Multiple Methods -  There are two sets of methods that are a little confusing: Add* and Set* methods. Also, there are two of each, that is, SetRow and SetRowV for example. Determine whether there needs to be these combination's and if we can simplify them.

* Indexing &#8211; Declaring Indices for columns seems to work. However, I'm not sure it has been implemented in all methods. The different combination of methods outlined in b) complicates things. Make sure indexing is implemented in all methods.
</description>
  <from-support type="integer">0</from-support>
  <id type="integer">388809</id>
  <importance type="integer">2</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">88333</milestone-id>
  <notification-list>abjj7GmAqr3PTNeJe5aVNr,apFgCgqb4r3Q6XeJe5afGb</notification-list>
  <number type="integer">2</number>
  <priority type="integer">3</priority>
  <reporter-id>abjj7GmAqr3PTNeJe5aVNr</reporter-id>
  <space-id>aldmmqpOGr3QkAeJe5afGb</space-id>
  <status type='integer'>4</status>
  <status-name>Test</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Make sure exiting details of ESI$IndexedTable are complete and correct.</summary>
  <updated-at type="datetime">2010-08-24T03:37:38-07:00</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>apFgCgqb4r3Q6XeJe5afGb</id><login>mcmanamon</login><login_name warning="deprecated">mcmanamon</login_name><name>mcmanamon</name></assigned-to>
  <reporter><id>abjj7GmAqr3PTNeJe5aVNr</id><login>tlwiechmann</login><login_name warning="deprecated">tlwiechmann</login_name><name>tlwiechmann</name></reporter>
</ticket>
<ticket>
  <assigned-to-id>apFgCgqb4r3Q6XeJe5afGb</assigned-to-id>
  <completed-date type="datetime"></completed-date>
  <component-id type="integer"></component-id>
  <created-on type="datetime">2009-06-01T05:05:48-07:00</created-on>
  <description>Enhancements &#8211; Add these new features.
* Column Typing - Add typing to a column. Builtin's (page 36 of the EsiObjects Language Guide) and Normal classes should be selectable. All columns should be typable. If a type is not specified, it should default to a string type.
* Column Type Validation &#8211; There should be a generic method that performs validation on a given column. It should act as if the column had a Property Sheet and the $Valid was coded. This should be accomplished in a general way that applies to any column type.
* Criteria Iteration &#8211; Finish up the criteria iteration. Currently, the normal iterator is implemented (have not tested it). First, please test the normal iterator and write regression test for it. Then implement the criteria iterators. Try to reuse the Base$Criteria objects. If that appears problematic, reimplemented them. However, please implement all of the criteria implemented under Base$Criteria.
* Event Processing &#8211; Event Processing should be integrated at the usual event points - storage, deletion, etc.</description>
  <from-support type="integer">0</from-support>
  <id type="integer">388814</id>
  <importance type="integer">3</importance>
  <is-story type="boolean">false</is-story>
  <milestone-id type="integer">88333</milestone-id>
  <notification-list>abjj7GmAqr3PTNeJe5aVNr,apFgCgqb4r3Q6XeJe5afGb</notification-list>
  <number type="integer">3</number>
  <priority type="integer">3</priority>
  <reporter-id>abjj7GmAqr3PTNeJe5aVNr</reporter-id>
  <space-id>aldmmqpOGr3QkAeJe5afGb</space-id>
  <status type='integer'>0</status>
  <status-name>New</status-name>
  <story-importance type="integer">0</story-importance>
  <summary>Add new features to ESI$IndexedTable.</summary>
  <updated-at type="datetime">2010-08-24T03:37:38-07:00</updated-at>
  <working-hours type="float"></working-hours>
  <working-hour type="float" warning="deprecated"></working-hour>
  <estimate type="string">None</estimate>
  <total-estimate type="float">0.0</total-estimate>
  <invested-hours type="float">0.0</invested-hours>
  <assigned-to><id>apFgCgqb4r3Q6XeJe5afGb</id><login>mcmanamon</login><login_name warning="deprecated">mcmanamon</login_name><name>mcmanamon</name></assigned-to>
  <reporter><id>abjj7GmAqr3PTNeJe5aVNr</id><login>tlwiechmann</login><login_name warning="deprecated">tlwiechmann</login_name><name>tlwiechmann</name></reporter>
</ticket>
</tickets>

