Some views and queries and such are stored in the database simply so Kentico can do what it needs to resolve macros in that text. If you're concerned with versions and losing code or content, take more frequent backups of your database.
Using the link I provided is more of a temporary, development solution. IMHO, you won't want those checked out when you deploy the site live and I believe Kentico states/suggests to check them in prior to publishing as well. Remember is a CMS, not a bunch of aspx or ascx pages you're creating. It's supposed to be dynamic.