Why aren't the languages in the database?

[PurpleEdge]

Hello,

It would be easy to read all the required language records on start-up into an array, so I doubt there is any performance hit at all. And backend management would be much easier, especially for end-users.

It was just a thought, I don't develop multi language sites at all, so it is not an issue for me.

[Stefek]

Hello Purple,

as Ruud said, it wouldn't make much sense to put the data into a database.

However, if you find the language management is too komplex as it is right now, have a look how it is handled in the Admin-Tool "Practical Module Functions" from User Thorn.
Espacially if you're after to create own modules, this Admin-Tool and its functions can be of interest for you.

It has a totally different approach on the language files and a language editor "console".

Kind regards,
Stefek

[Ruud]

it is a bit "expensive" to put messages in a database.

The languages are mainly just words or very small sentences. But it could be we need 100 or more of those to build a page. (especially in the backend)
That would need 100 queries to the database, instead of a single read of the language file.

Messages do not change frequently, so there is no real advantage in making a complete database management for it.

[PurpleEdge]

Is there a good reason why the languages aren't in a datafile?

Wouldn't it make management much easier?