+2  A: 

This will depend:

You mention: "where kysymys is a question in English."

Are you planning to have the same question in other languages?

If that's the case, normalize the question and question body out to another table. That way, given a language and a question ID, you can retrieve the right one.

However, if the question is only going to be in English, just leave it in the same table. That's perfectly fine.

thedz
I am not planning to have the same question in many languages. --- My table contains some Finnish because I need to explain it to people who do not understand English.
Masi
In that case, I'd just leave it in the same table. There's no point in normalizing it out to another table.
thedz
+1  A: 

Are you planning to store revisions of a question ? e.g. StackOverflow allows you to revise the question text and it stores the history.

If this is the case I would store the text separately. You would store answers/comments referenced against the question-id, but the question text would be held in a separate table.

Your data neutralisation issue (above) is orthogonal to this (a separate issue of data sanitisation/cleansing).

Brian Agnew
Thank you for pointing that out! -- I want to build a system which I can extend in the future. I will put the questions to a separate table.
Masi
Glad to be of help. I usually normalise data in databases early and collapse later if/when I realise that level of indirection is not required or not optimal
Brian Agnew