Hi Ted,

Let me share my experience with you: I have stumbled on the exact same
problem, with sometimes millions of warnings when loading geographical
data into a table with decimal fields. In the end, it is no big deal:
either the input data has more decimal digits than your destination
field and it gets properly truncated, or it's empty and gets converted
to 0. Depending on your application requirements, you might want to
change the 0 values to NULL after loading the initial data.

Warning 1265 is really just a note to get your attention at the loss of
precision; after you analyze the situation and understand what is
happening, you can safely ignore it.

Hope this helps,

JFG