UpValues evaluation with Dot operator

Question

I would like to simplify some database notation, and I'm doing some tests with UpValues for that.

For example, if I set this Upvalue fot tab1:

tab1 /: tab1.column1 = 1

When I evaluate

tab1.column1

I get 1 as expected. But if later I set column1 = "x", when I evaluate it again, I get tab1."x" instead of 1 as I need.

There is some way that I can change this behavior? So I could get 1 and prevent variables name conflict?

Update

To avoid misinterpretation here is the evaluation sequence.

Quit the kernel and evaluate:

tab1 /: tab1.column1 = 1;
column1 = "x";
tab1.column1 

The result is tab1."x" in the first evaluation.

Answer 1

You could do:

Unprotect[Dot];
SetAttributes[Dot, HoldAll]

Then

   tab1 /: tab1.column1 = 1 ;
   column1 = "x";
   tab1.column1

returns 1

Is this what you want?

Answer 2

You could introduce your own notation. Something like the following.

SetAttributes[qualifed, HoldAll]
Needs["Notation`"]
Notation[ParsedBoxWrapper[
  RowBox[{"u_", "∘", "v_"}]] \[DoubleLongLeftRightArrow] 
   ParsedBoxWrapper[RowBox[{"qualifed", "[", RowBox[{"u_", ",", "v_"}], "]"}]]]
TagSetDelayed[qualifed, qualifed[u_, v_] = val_, TagSet[u, qualifed[u, v], val]]

tab1∘col1 = 1; tab1∘col1

1

col1 = 42; tab1∘col1

1

tab1∘col1 = 42; tab1∘col1

42

I'm using \[SmallCircle] (∘) in place of dot (.). It can be entered with [esc]sc[esc]. I've tested this only a little. I'm not sure it's foolproof.

Answer 3

Are you sure you're not looking for this:

tab1 /: tab1.column1_ := 1;

That is whatever column1 binds to rather than the literal column1?

this way

tab1."x"

evaluates to

1