Hello,
I don't understand why location module have the country and regions in files (location/supported/). That's for performance reason? But if you have all or a lot fo country activate, performance still ok with all this include?
DB isn't a better choice for import/export, extensibility and communication between other module....
And why don't eliminate completely the country files? For formating and country special case, http://www.ubercart.org have a nice little pattern system.
Comments
Comment #1
gagarine commentedAn example of country information (or import?) file for ubercart: http://www.ubercart.org/files/italy_380_1.cif
Comment #2
nicholasthompsonI've also wondered this.
When looking up states (for example), would it not be more efficient to fire off 1 DB Query rather than including an array of hundreds of items?
Comment #3
bdragon commentedI agree, it's inefficient.
It will be changing soon. At the very least, all the "common" stuff like region names can be moved into a table.
Comment #4
gagarine commentedNice!
Comment #5
Kerel commentedThat would give a lot of advantages indeed!
May be also look at the possibility to include cities in the database to extend the scope of this module.
Comment #6
yesct commentedtagging.
Comment #7
clashar commentedsubscribe
Comment #8
gagarine commentedComment #9
suffering drupal commentedThe typical state/province field is rather limited and offers only mandatory options.
Is there a way to manually add an additional "Region" field (to location, not CCK) somehow? To enable the use of for example Yellowstone Park, Patagonia, the Alps, Côte d'Azur, Veluwe, Toscana, Costa del Sol and all those other marvelous regions that are not politically defined, but generally more interesting.
Comment #10
gagarine commentedThey are also a http://drupal.org/project/countries field now
Comment #11
suffering drupal commentedNo regions however, right?
Comment #12
suffering drupal commentedI get it, it has to be handmade, yes?
Comment #13
legolasboClosing old D6 issues as D6 is end of life