![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've been trawling back!dmh!hdr!dm0c.h to try and find where all the unicode fields are stored in the configuration file. Other than the default unicode collation field I have been unable to determine where I would find the flags indicating if the database is unicode enabled and what the normalizattion scheme is. Would they be buried in the dbservice field? |
#3
| |||
| |||
|
|
I've been trawling back!dmh!hdr!dm0c.h to try and find where all the unicode fields are stored in the configuration file. Other than the default unicode collation field I have been unable to determine where I would find the flags indicating if the database is unicode enabled and what the normalizattion scheme is. Would they be buried in the dbservice field? |
#4
| |||
| |||
|
|
I've been trawling back!dmh!hdr!dm0c.h to try and find where all the unicode fields are stored in the configuration file. Other than the default unicode collation field I have been unable to determine where I would find the flags indicating if the database is unicode enabled and what the normalizattion scheme is. Would they be buried in the dbservice field? |
#5
| |||
| |||
|
|
And it also occurred that what can be read can be written so the module could then be extended to simple writes to a configuration file...alter the database id, extent paths that sort of thing. Is that cool or what? |
#6
| |||
| |||
|
|
Martin Bowes wrote: And it also occurred that what can be read can be written so the module could then be extended to simple writes to a configuration file...alter the database id, extent paths that sort of thing. Is that cool or what? That is cool, to be sure. Years ago Karl wrote a little tool that did some of that; you might ask him about it, though I vaguely recall him giving all kinds of timid-sounding caveats about it being for Unix only and not thoroughly tested and "you'd be on your own" etc. |
#7
| |||
| |||
|
|
Martin Bowes wrote: And it also occurred that what can be read can be written so the module could then be extended to simple writes to a configuration file...alter the database id, extent paths that sort of thing. Is that cool or what? That is cool, to be sure. Years ago Karl wrote a little tool that did some of that; you might ask him about it, though I vaguely recall him giving all kinds of timid-sounding caveats about it being for Unix only and not thoroughly tested and "you'd be on your own" etc. |
![]() |
| Thread Tools | |
| Display Modes | |
| |