Skip to main content
edited tags
Link
Jack Douglas Mod
  • 40.2k
  • 35
  • 59
Tweeted twitter.com/#!/StackDBAs/status/496733121656930304
added 32 characters in body
Source Link
Colin 't Hart
  • 9.4k
  • 13
  • 13

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object, but there's already a tag which can be used in some cases for this, or just use .
  • index access paths, where I think the tag is extraneous. or similar should be enough.

If it was up to me, I would remove this tag and blacklist it.

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object, but there's already a tag for this.
  • index access paths, where I think the tag is extraneous. or similar should be enough.

If it was up to me, I would remove this tag and blacklist it.

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object, but there's already a tag which can be used in some cases for this, or just use .
  • index access paths, where I think the tag is extraneous. or similar should be enough.

If it was up to me, I would remove this tag and blacklist it.

added 140 characters in body
Source Link
Colin 't Hart
  • 9.4k
  • 13
  • 13

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object, but there's already a tag for this.
  • index access paths, where I think the tag is extraneous. or similar should be enough.

If it was up to me, I would remove this tag and blacklist it.

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object
  • index access paths

If it was up to me, I would remove this tag and blacklist it.

The tag has no description and I've seen it used in at least three different contexts:

  • Microsoft Access, but there's already a tag for this.
  • privileges a user has on an object, but there's already a tag for this.
  • index access paths, where I think the tag is extraneous. or similar should be enough.

If it was up to me, I would remove this tag and blacklist it.

Source Link
Colin 't Hart
  • 9.4k
  • 13
  • 13
Loading