relpipe-data/examples-tr-sqlite-custom-version.xml
branchv_0
changeset 297 192b0059a6c4
parent 286 37c50bb1f36f
equal deleted inserted replaced
296:418e11eb6fea 297:192b0059a6c4
     9 	<text xmlns="http://www.w3.org/1999/xhtml">
     9 	<text xmlns="http://www.w3.org/1999/xhtml">
    10 		
    10 		
    11 		<p>
    11 		<p>
    12 			One of reasons why we prefer shared libraries (<code>.so</code>) rather than static linking,
    12 			One of reasons why we prefer shared libraries (<code>.so</code>) rather than static linking,
    13 			is that shared libraries are much more hacker-friendly and allow the user switching to a newer or modified library without recompiling the program.
    13 			is that shared libraries are much more hacker-friendly and allow the user switching to a newer or modified library without recompiling the program.
       
    14 		</p>
       
    15 		
       
    16 		<p>
       
    17 			<strong>
       
    18 				n.b. This method is obsolete since <m:a href="release-v0.16">v0.16</m:a> that does not use SQLite library directly 
       
    19 				and uses arbitrary database driver (including SQLite one) through an abstraction layer (ODBC).
       
    20 				This article is still valid as an example of the LD_PRELOAD hack and can be used with older versions of <m:name/>.
       
    21 				Since v0.16 we can easily replace whole ODBC driver (and thus use also different version of the SQLite),
       
    22 				there is no need for LD_PRELOAD hacking
       
    23 				– we can just configure desired driver (the <code>.so</code> file) in the INI file or ad-hoc in the connection string.
       
    24 			</strong>
    14 		</p>
    25 		</p>
    15 		
    26 		
    16 		<p>
    27 		<p>
    17 			By default, <code>relpipe-tr-sql</code> links to the SQLite library available in our distribution (e.g. 3.22).
    28 			By default, <code>relpipe-tr-sql</code> links to the SQLite library available in our distribution (e.g. 3.22).
    18 			As we can check:
    29 			As we can check: