If you're using DBI, you can also create a table with three rows:

• XCOORD
• YCOORD
• TERRAINTYPE

Then, you don't have to worry about memory problems - MySQL does it for you. However, you do have the speed-hit from using DBI for simple queries.

A possible solution to that would be to cache a NxN area around your intrepid explorers and grab that whenever they leave it.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.