My cousin Will has been staying in Melbourne for the last few weeks so I wanted to make sure we had the chance to get out of the city and see a good part of the Aussie bush. For a weekend trip from Melbourne the most obvious choice is the Grampian's National Park. If you're looking for a good fishing spot in this South East corner of Australia, at the moment Lake Wartook is a bit of a sure fire bet. We even had 700g - 1kg Rainbow Trout taking worms as bait, no lure, no fly! Now that sure does mean that this lake is just full of fish!
We heard from a local that they had recently stocked the lake with Rainbow Trout and our camp fire dinner that night was definately a testamount to that. Check out the photos...
I stumbled upon a web survey being conducted by A List Apart today. It's great to see people taking the growth and future direction of the web industry in this kind of light. I often try and relate the nature of this industry to the early 'wild west' days of the industrial revolution. This industry is still very young and is inevitably still finding it's feet. It's great to see surveys like this that take such a proactive approach to learning about the current state of the industry and also try and determine it's future direction in a objective non-biased way.
Add your bit - complete the survey below...
This morning a colleague and I discovered that it is possible to modify database objects (Tables, Views etc...) via the Eclipse DB Browser perspective. Up until now we thought that this was "read-only" functionality.
It turns out that if you open the select statement of a view, for example, change the select statement for whatever reason, and then save, upon saving it will actually modify the view in the database. You may say that this sounds obvious, and it sounds as if it is, however up until now we have assumed that it's not possible to modify these objects via the DB Browser.
The main problem here is that you may inadvertently modify a view in Oracle / SQL Server, and then break application functionality and/or unit tests.
To get around the problem, create a read only user account in the database and use that to connect via DB Browser.
