I don't know if I should be very irritated or what. I single handedly built over 300 queries for a large database, and developed a naming convention so I could find them later. No one else in my office even knows how to build a query, but I came in yesterday to find that all of them had been renamed. I am now having a very hard time finding things, and I am trying to figure out what to do.

I spoke with the person responsible, and she just downplayed the whole thing. She said she renamed them so she can find them more easily. Unfortunately, I am the only one who knows how to build, edit, and maintain them, and the only reason she needed to find them was to test the queries. The new naming convention doesn't make sense at all, and I feel like we have taken a backwards step in the development process. 

What I'm trying to figure out is:

1) Am I overreacting?

2) What is the best way to handle this? I hate to mention this to my boss, but after speaking with my co-worker yesterday, I can already tell she feels like she did nothing wrong.

Why don't you simply handle it like adults: sit down, non-confrontationally, and come up with a list of pros and cons for a naming scheme , agree on one and make it official by writing a short document describing it. Elicit genuine interest in her input so she feels (and is) involved. 

If it's mostly a matter of taste and if she's the kind of person who absolutely has to have things her way, then just be glad that you're the bigger person and let it go. Life's too short to have a pissing contest of naming schemes.

Is the problem the naming scheme or that you feel you don't get any respect? If so perhaps you can work on your working relation. If you feel it isn't worth it then why do you care about what she thinks anyways? :) Another option might be that she truly doesn't feel it's a big deal and if you explain nicely that you're having trouble finding stuff perhaps you can change it back.
