Hi All, I'm faced with the situation where I'd like to detach the CP used in DB tables from the CP used in other parts of the system, f.e. the CP used to encode human readable strings in source code.
[ The reason are that I decided to make the CP transition gradual, without converting several gigabytes of database together with the app, plus I can of switching to UTF-8 for strings used in source, I wouldn't like to switch to UTF-8 for the database yet, because all strings would become variable length. ] So, my current choice is to extend all DBCREATE(), DBUSEAREA(), HB_DBCREATETEMP() and __DBOPENSDF() calls with the (dirty) Harbour <cCodePage> parameter extension. For one thing this is quite error prone, as I may miss a few occurrences (or ones stored in lib code f.e.) thus corrupting the database. Second: I prefer not to use such dirty extensions. This matter could be quite easily and cleanly solved with a app global Harbour setting, which would set the _default_ CP used in all DB operations. (just as we can f.e. have default shared mode set in _SET_EXCLUSIVE, since Clipper times) So, I'd like to add a _SET_DBCODEPAGE setting which would control this centrally, cleanly and by eliminating all potential errors resulting in mass source code modification. The default value for this setting would be a neutral value (NIL/NULL), which means Harbour would behave exactly the same it is now, if someone doesn't use the setting. The modification looks quite easy to make, so I can implement it. Any opinions or objection? Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
