Jump to content

Recommended Posts

Hi all -

 

I'm writing a little piece of blog software for the pastor of my church, and I'm wondering database-wise how to attack it.  When it comes to performance, when you have a small amount of rows being returned from a relatively small dataset, is it more efficient to store everything in one table?

 

id (PK)

date (date)

title-es (varchar)

title-en (varchar)

post-es (text)

post-en (text)

author (enum)

category (varchar)

active (bool)

 

The main question I'm concerning myself with is to split the languages or not.

 

Thanks!

The table looks pretty good, however, I'd do something like this:

 

id (PK)

date (date)

title (varchar)

post (text)

author (enum)

category (varchar)

active (bool)

language (varchar) - this can be es/en, or, whatever languages you might come up with in the future

 

It should make your coding much easier :)

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.