Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
DB Files

Posted by TedH (TedH), 16 November 2006
Hi Graham, just an out of interest guestion. I use .txt files to store the database for each month's entry on my blog. Can I use .db instead or is that reserved for stuff like MYSQL?

If I can, it would make searching my archive folders a whole bunch easier as all I'd need to look for are .db files.

cheers - Ted

Posted by admin (Graham Ellis), 16 November 2006
Not sure what OS you're using, but typically the actual extension letters won't make much of a difference ... and they certainly won't make any difference to Perl.  By all means use a different extension to distinguish the special format files

Posted by TedH (TedH), 16 November 2006
Server is Linux(Unix)/Apache. I heard that Unix allows me to 'invent' extensions - but I've always been a bit leary of that.

I know I can have them on my PC's local testbed server and they're treated as text files. But once online I'm not really sure what the Unix is gonna think of it.

Posted by Custard (Custard), 16 November 2006

Unix really won't care what you call your file.

To unix, all letters(*) in a filename are equal, and the extension means nothing.   It's humans who like the extensions so they can tell at a glance what may be inside the file.
In unix, use 'file <filename>' to see what it thinks is in the file (**)

If you are serving the files from Apache however, take a look at the conf/mime.types file. This tells the browser via the webserver what to do with a file based on its name.

So name your files however you like but try not to confuse yourself when you expect one type of data in a file with another name


(*) With the possible exception of files that start with a '.'.  These files are normal files, but do not appear in normal directory listings. You need to specify ls -a to see them. But for all other purposes they are normal files too.
(**) It does this by looking up 'magic' numbers. See man magic(4)

Posted by TedH (TedH), 16 November 2006
Hi Custard, thanks.

Locally my mime file I can see, but my online server may be a different matter. Good TS though, so they'll help me on that.

cheers - Ted

See you Geekmas?

This page is a thread posted to the opentalk forum at and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: • WEB: • SKYPE: wellho