drwex | What would _you

Here's a quickie. I need a name for something. You're restricted to two relatively common words, though jargon is allowed. For now we'll call it $NAME

You have a number of values in a table. These values came from us, the software supplier, and from you, the customer. Periodically we'll give you an upgrade to your data, including replacement values for things in this table. We also give you a flag, $NAME. If $NAME is true/on/set then at the next upgrade whatever the associated data value is, it'll be overwritten by a new value we supply. If it's false/off/unset then the data will be preserved. If you set this flag on your own data it has no effect.

So the cases are:
1. Our data, flag set -> overwrite at upgrade time
2. Our data, flag unset -> leave alone at upgrade
3. Your data, flag any value -> leave alone at upgrade

So, dear readers, what would YOU call $NAME? (Remember you're limited to two words, and no German so upgradenflaggensetten is right out.) I'd tell you what we call it now but that would probably bias responses too much.

Flat | Top-Level Comments Only

From:

ciani.livejournal.com

why not keep or persist with an on/off toggle?

drwex

Because both keep and persist are too generic. Lots of things are kept or persisted.

quietann.livejournal.com

Ok, not a programmer here at all, but this sounds like you are working with default data (that is, what you call "our data" is a default data set supplied by your company.) So, "Upgrade Default" ???

ariesd.livejournal.com

Is the question simply what to name the variable that is set high when you are looking to refresh the table? If that is all that this is used for maybe a local variable $UPDATETABLE and beyond that if it were global $UPDATETABLE_TABLENAME, a simply TABLENAME to differentiate it from other table update flags if it were global and couldn't be recycled.

No, it's not quite that simple. It's a name that has to be shown to people most of whom are administrators of some kind, but few of whom are actual DBAs.

hmmmm, "UPDATE_TABLE" is short and to the point. Clear enough, is the length of the name in issue?

Yeah, except it's not the table that's being updated, it's the data value(s) shown in the form, which might be spread across multiple tables. So the effect of the checkbox applies to one or more rows in one or more tables, which might change with the next schema upgrade.

ah ok, I thought looking at it was still backend looking at it, not at the API level. I think the choice "Upgrade Allowed" is simple enough and user friendly.

So curious what the old name was that you couldn't have too long of a name w/o modifying the input boxes.

It's currently called "system lock"

yeah It could be improved. :)

catya.livejournal.com

i might do something like "overwrite default settings" or "overwrite defaults" for short? But it depends on what the data you are talking about overwriting is..

Nod. I've been thinking about "overwrite on upgrade" but that's too long to fit most places. I'm trying to avoid having to redesign half a hundred input dialogs just to get one label change.