Hi,
We are using Sybase 12.5.4 how to mask a column of a particular table,
plz provide any link or manual for the same.

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

<raghusql1 (AT) gmail (DOT) com> wrote

What do you mean by "mask"? Encrypt it? Perhaps revoking all privileges on
the table and granting privileges on a view that excludes the one column of
the table. However, inserts might not be doable since instead-of triggers
starts with 15.0.2. FGAC (license needed) might be another possibility.
12.5.4 documentation is at
http://infocenter.sybase.com/help/in....5.4/title.htm

On Oct 27, 9:35*pm, raghus... (AT) gmail (DOT) com wrote:
Please define "mask"?

Are you looking to prevent users from seeing certain data (you can
revoke select permissions at the column level, or create a view that
substitutes
some value for a column based on the user_id() of the person doing the
select.)
You can also upgrade to 15.0 and use the new encryption features. The
encryption
feature includes a default value provided to users without decrypt
permission.

Or are you trying to use a bit-mapped column (similar to
sysusages.segmap) and
mask certain bits? If so see the & and ^ operators

<int> & 1 returns 1 if bit 0 is on
<int> & 2 returns 2 if bit 1 is on, etc.
<int> & 3 returns 3 returns 1 if bit 0 is on and bit 1 is off, 2 if
bit 0 is off and bit 1 is on, and 3 if both bits are on...
[etc.]

-bret