Search the Community
Showing results for tags 'Static data'.
What is the best way to manage larger amounts of constantly necessary static data. I.e. Countries and there depending states and the cities in those states with their postal codes which needs to also translatable into different languages. I.e. Germany, Deutschland, Allemagne, ประเทศเยอรมัน North Rhine Westphalia, Nordrhein Westfalen, ... Cologne, Koeln ,... ... Or Mr., Miss., Mrs., Or Other clearly defined lists of static data i.e for Taxes or Currencies, which would be used over and over again in several site I.e in Search forms, mail forms, user profiles, shops, realestate lists, .... All this data won't change over years. One way would be to create pages the processwire way and than search for them an make a search so that a parent shows only the subpages assigned to him. What about scalability? I.e if you have clearly defined job descriptions - about 30 TSD. Is there already a module taking care of such kind of static data which probably get much better stored as is in a table direct in the database? Imho it does not really make sense to create for each item a page. What is your opinion? How do you handle that static data in your sites? Thanks Andi