0

I'm trying to create a database that has to contain articles in different languages. I'm using Mariadb as my server and I know bits of SQL. My knowledge doesn't really cover details like the differences between engines like MyISAM, InnoDB etc or character sets like utf8/16/32, latin 5/7/etc. I do know that the character set has importance, I guess what I'm looking for is an all-encompassing character set and an engine that best deals with this type of content.

Also, is there an advantage in storing articles in multiple data rows (equivalent of different pages) to make things a little faster, or would you store a whole article in a single data row. Or does that depend on the size of the articles?

Sorry for my noobish question, I know the information is all out on the internet but it would take me quite a long time to research and get a grip on everything. Would be cool if someone with experience could give me a little head start and point me in the right direction. This is for a intranet site, consider the content to be somewhat like a blog (and no, I don't want wordpress or something similar at this point).

Not sure if it matters, but I tend to create and manipulate my tables with phpmyadmin, I use apache as web server and it all runs on Linux.

Jakke
  • 990
  • 1
  • 7
  • 17
  • If it's convenient for you, split articles. If it's not, don't split them. Premature optimization is the root of all evil. – gronostaj Aug 21 '14 at 09:58
  • Thanks for the info... but I'm not sure I understand your statement. I would think that it's a lot more difficult to change a working system than to implement it right from the first time, that's why I asked. My preference is to keep everything in single records without splitting to keep things simple (KISS). In case the layout of the site should change, rearranging the records could be a huge task. That being said, I could see that not splitting could potentially have a performance impact. – Jakke Aug 22 '14 at 03:18

1 Answers1

1

Use utf8 and you should be good to go. It supports more languages than you can shake a stick at. MyISAM and InnoDB both seem support it according to the MySQL docs, though I only have Postgre experience.

JongleurX
  • 36
  • 3