I'm not sure whether this has been discussed, but here goes.
I would like to talk about having multiple (language) versions of the information on a item in the database.
Having worked on large web sites using technologies like Vignette I must stress how versatile this product is (that I have invested in and do in no way regret).
Also even though the comparison is fairly difficult with products like Vignette, the type of project I was working on was fairly close to what I would like to use Links SQL for (and am near to succeeding in doing so).
This question however covers an area I feel could be improved/modified. More and more web sites will be opening up to the world, and will require localisation efforts. One of the first measures is to provide existing information in the local language. Although this may be seen as a more database structure requirement it also requires in my view a slightly different approach of the Links SQL product itself. I must stress the word slightly because there really do seem to be numerous ways to deal with providing multi-lingual versions of a same item (just in case you perl cracks thought I was saying the opposite).
I think the default database structure should be multi-lingual rather than set up for only one langauge, but maybe two database structures should be offered and the initial setting up of the database requires the user to indicate whether he/she would like to use more than one language. However most users will probably agree that changing from multi-lingual to one language would be a nightmare from a database point of view.
I would be interested to know what other users of LinkSQL think of this or if other users have modified their database structure in order to accomodate multi-lingual versions of an item in their database.
Jag
I would like to talk about having multiple (language) versions of the information on a item in the database.
Having worked on large web sites using technologies like Vignette I must stress how versatile this product is (that I have invested in and do in no way regret).
Also even though the comparison is fairly difficult with products like Vignette, the type of project I was working on was fairly close to what I would like to use Links SQL for (and am near to succeeding in doing so).
This question however covers an area I feel could be improved/modified. More and more web sites will be opening up to the world, and will require localisation efforts. One of the first measures is to provide existing information in the local language. Although this may be seen as a more database structure requirement it also requires in my view a slightly different approach of the Links SQL product itself. I must stress the word slightly because there really do seem to be numerous ways to deal with providing multi-lingual versions of a same item (just in case you perl cracks thought I was saying the opposite).
I think the default database structure should be multi-lingual rather than set up for only one langauge, but maybe two database structures should be offered and the initial setting up of the database requires the user to indicate whether he/she would like to use more than one language. However most users will probably agree that changing from multi-lingual to one language would be a nightmare from a database point of view.
I would be interested to know what other users of LinkSQL think of this or if other users have modified their database structure in order to accomodate multi-lingual versions of an item in their database.
Jag
Multi-Language versions of an item