Well, you could try aliasing via a projection? i.e. in your LINQ, doing
something like:
               select new {
                   p.MyCharColumn, // default name
                   Bar = p.Foo // aliased
               };

However! The aliases that it uses in the SQL are largely an implementation
detail. As far as I can see, it would be perfectly reasonable for the LINQ
provider to use "c0", "c1", "c2" etc for the columns: as long as it can map
them back to the members in your object model it is none of our business how
it handles it (encapsulation).

IIRC, from inspection I believe LINQ-to-SQL tends to honour aliases, but I
doubt it is guaranteed; what DbLinq does is anyones guess.

Marc