0

I'm modeling a database and I have these three fields (among others):

  • created_by,
  • updated_by, and
  • deleted_by.

I'm using author as an alias for "created_by", and editor as an alias for "updated_by". What choices do I have as an alias for "deleted_by"?

RegDwigнt
  • 97,231
  • 5
    Given these are just programming identities, perhaps it would have been better to go for consistency right from the start - created_by: creator, edited_by: editor, deleted_by: deleter** (where deleter/deletor has been asked about on ELU before) – FumbleFingers Dec 10 '13 at 00:52
  • 1
    What was wrong with the natural deleter in the first place? You need not have looked it up anywhere, it should have occurred to you as the natural choice? (I happened to see this post just now.) – Kris Dec 10 '13 at 05:36
  • @FumbleFingers In the given context, the "word" editer with an e is also sometimes used, to distinguish from the usual editor. – Kris Dec 10 '13 at 06:21

2 Answers2

5

*What choices I have to aliase deleted_by?*

censor, scrubber, excisor, witholder, concealer, expurgator, excinder, publisher, appraiser.

anongoodnurse
  • 55,278
2

It looks as if you are using a fairly straightforward CRUD model of the data lifecycle (create, read, update, delete). If so, then my primary suggestion would be to stick with the agent nouns that are obvious and a bit odd, but therefore also clear and distinctive: creator, reader, updater and deleter. Within the technical environment of your project, these would have usefully unmistakeable meanings.

In the spirit of your other 'aliases', however, and because in data processing this deletion means the end of that item's existence, instead of 'deleter' I am inclined to suggest 'terminator'...

  • Oh, and 'retrieve' is sometimes used instead of 'read', in this context, so (if you are using that bit of the CRUD model) 'retriever' might be a usefully distinctive term instead of the relatively vague 'reader'. – Captain Cranium Dec 23 '15 at 15:38