| … | |
… | |
| 87 | Request has reached the end of its lifetime and holds no resources |
87 | Request has reached the end of its lifetime and holds no resources |
| 88 | anymore (except possibly for the Perl object, but its connection to |
88 | anymore (except possibly for the Perl object, but its connection to |
| 89 | the actual aio request is severed and calling its methods will |
89 | the actual aio request is severed and calling its methods will |
| 90 | either do nothing or result in a runtime error). |
90 | either do nothing or result in a runtime error). |
| 91 | |
91 | |
| 92 | FILENAMES/DATABASE NAMES |
92 | WIN32 FILENAMES/DATABASE NAME MESS |
| 93 | The BDB expects "binary" filenames (octet strings) for pathnames on |
93 | Perl on Win32 supports only ASCII filenames (the reason is that it |
| 94 | POSIX systems, and "unicode" filenames (strings with characters |
94 | abuses an internal flag to store wether a filename is Unicode or ANSI, |
| 95 | potentially >255) on Win32 (expecting a Unicode win32 build - win32 is a |
95 | but that flag is used for somethign else in the perl core, so there is |
| 96 | total mess). |
96 | no way to detect wether a filename is ANSI or Unicode-encoded). The BDB |
|
|
97 | module tries to work around this issue by assuming that the filename is |
|
|
98 | an ANSI filename and BDB was built for unicode support. |
| 97 | |
99 | |
| 98 | BERKELEYDB FUNCTIONS |
100 | BERKELEYDB FUNCTIONS |
| 99 | All of these are functions. The create functions simply return a new |
101 | All of these are functions. The create functions simply return a new |
| 100 | object and never block. All the remaining functions take an optional |
102 | object and never block. All the remaining functions take an optional |
| 101 | callback as last argument. If it is missing, then the function will be |
103 | callback as last argument. If it is missing, then the function will be |
