Using a database doesn't by default make your site searchable. It's a more efficient storage system (usually) than having a bunch of static files.
SQLite is an easy way to develop, especially if you're running Python 2.5, but I usually move to a PostgreSQL backend for "production" sites, since SQLite doesn't allow for password protection of the database. Oh, and Django does most of the SQL heavy lifting for you, so it's not as if you need to become proficient in it before developing something. Just glance at the SQLite documentation, and when you're in your database, make sure to type ".databases" (everything inside the quotes) to see the path to your database, so you can put it in your settings.py file. On Fri, Apr 11, 2008 at 1:56 PM, sebey <[EMAIL PROTECTED]> wrote: > > you make a good point i will say but I have a few reasons for this: > > 1.I try and keep things easy > 2. I don't want them to be searchable(I know that sound odd but I my > site is designed so that I do not have the need for search > 3. I don't really want to add another thing to my "to learn list" as > well I have enough on my plate already > > but a remark on point three SQLite looks like a solution to my > problem,am I correct? > > On Apr 11, 11:45 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > > > > On Fri, Apr 11, 2008 at 5:20 AM, sebey <[EMAIL PROTECTED]> wrote: > > > i am on a mac and I am running a podcasting network so I will proabley > > > be storing all my files in XML/RSS > > > > I think you're suffering from very severe conceptual confusion. > > > > Take a podcast and think about it logically: > > > > Each podcast has a name. > > Each podcast has one or more "authors". > > Each podcast has one or more "episodes". > > > > Each "episode" has a publication date and an audio file, and maybe > > some other metadata. > > > > The logical way to build this, then, is to set up database tables > > which store this information, and then query it to dynamically > > generate an up-to-date feed, and that (modeling data for storage in a > > database, inserting it through a web-based interface, querying it back > > out again and rendering it into the output format of your choice > > through a templating system) is what Django is good at. > > > > -- > > "Bureaucrat Conrad, you are technically correct -- the best kind of > correct." > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
