, , , , ,

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

Industry Standard for AppRow? (OpenInsight 32-Bit)

At 09 JUN 2006 12:29:04PM Wayne Shepard wrote:

The repository doesn't like keys with more than three asterisks in the key. When you create an AppRow repository record for a row that has a multipart key, the asterisks in the row key must be converted to another character. What is the industry standard (if any) for what character to convert it to?

At 09 JUN 2006 01:04PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Underscore

The Sprezzatura Group

World leaders in all things RevSoft

At 09 JUN 2006 01:33PM dsig@sigafoos.org wrote:

and what happens if you have underscore in your id?

At 09 JUN 2006 01:35PM Wayne Shepard wrote:

I don't want to use underscore because underscore is already used in the key parts. I need to use a character not used in any other key parts which also doesn't have any other side effects in the system. I'm tempted to use "at" sign (@) or the pipe (|), but I'm wondering if people know of any other considerations. Is there an alternate industry standard?

At 09 JUN 2006 01:55PM Gerald Lovel wrote:

While the Repository identifier of the record would have "*" replaced with "_", The Repository record contains a copy of the original key.

At 10 JUN 2006 09:34AM support@sprezzatura.com wrote:

I think by underscore, my colleague meant colon. That's how the SYSENV items that ship with OI are delimited.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

<img src=http://www.sprezzatura.com/zz.gif"

At 14 JUN 2006 05:07PM Wayne Shepard wrote:

Yes, but it seems the colon is used to separate a table name from a row id. It has a specific purpose. Another character needs to be used to represent the asterisks.

At 15 JUN 2006 03:30AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Wayne,

The system uses two parts to resolve APPROW entities - the table nme and row ID….

1) The table name is stored in the ENTITYID field as everything upto the first ":" character. Anything after this is ignored when resolving - so we just usually convert "*" to "_" and leave it at that, as that's the character that will cause the REPOS_BFS to throw an error (repos keys can't have more than 4 parts).

2) The actual row ID is stored in the SUB_KEY field.

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the Works forum...