Re: [midgard-user] Question about repligard safe apps

[James Gifford]

Hi dudes

I'll have to explain my question better.

I use the article table to store a number of things that it was not intended for:
- the print field and the extra1 field hold the topic ids of secondary and tertiary topics  
- the view field holds the number of days until the article needs to be reviewed (like the caldays field)
- the icon field holds a boolean value (1 or 0) depending on whether I want a thumbnail images displayed in the article

My question is: how does repligard deal with these fields?

**Print Field**
In the manual, the print field is

An integer, originally pointing to a printable version ID of this article.

So does repligard replace that id with the different article id in the live db based on the GUID of the printable version?  In other words, you should only use this field to store other article ids?

**Icon field**
In the manual, the icon field is

   An integer, originally pointing to an icon ID for this article

So does repligard replace this id the with different attachment id in the live db based on the GUID of the attachment?  Therefore, this field should only be used to store attachment id?

**View field**
In the menu, the view field is:

An integer, originally pointing to a "view" ID for this article.

Like print, should this field only be used for article ids?  I kind of understand why you might want a print version (through applying a different style is much more sensible).  But what is the reason behind the view field? How was it originally intended to be used?

So I briefly tested these theories and it appears that repligard doesn't alter these fields but that could just mean that those particular ids are the same in both live and staging.

I hope someone can make sense of this!

Thanks
James