Prepare some notes for the new virtualfull feature

[bacula/docs] / docs / manuals / en / misc / internaldb.tex

diff --git a/docs/manuals/en/misc/internaldb.tex b/docs/manuals/en/misc/internaldb.tex
index 65cd0ea004a5948e76c7f60d0ad4673cb7b2192a..fc21967914aab91f2135a77fe6440c705a3d35bd 100644 (file)
--- a/docs/manuals/en/misc/internaldb.tex
+++ b/docs/manuals/en/misc/internaldb.tex
@@ -1,6 +1,3 @@
-%%
-%%
-
 \chapter{The internal database is not supported, please do not
 use it.}
 \label{InternalDbChapter}
@@ -9,68 +6,28 @@ do not }
 \index[general]{The internal database is not supported, please do not
 use it. }
 
-\section{Internal Bacula Database}
+\section{Internal Bacula Database}\label{chap:InternalBaculaDatabase}
 \index[general]{Internal Bacula Database }
 \index[general]{Database!Internal Bacula }
 
 Previously it was intended to be used primarily by Bacula developers for
 testing; although SQLite is also a good choice for this. We do not recommend
-its use in general. 
+its use in general.
 
 This database is simplistic in that it consists entirely of Bacula's internal
 structures appended sequentially to a file. Consequently, it is in most cases
 inappropriate for sites with many clients or systems with large numbers of
-files, or long-term production environments. 
+files, or long-term production environments.
 
 Below, you will find a table comparing the features available with SQLite and
 MySQL and with the internal Bacula database. At the current time, you cannot
 dynamically switch from one to the other, but must rebuild the Bacula source
 code. If you wish to experiment with both, it is possible to build both
-versions of Bacula and install them into separate directories. 
-
-\addcontentsline{lot}{table}{SQLite vs MySQL Database Comparison}
-\begin{longtable}{|l|l|l|}
- \hline 
-\multicolumn{1}{|c| }{\bf Feature } & \multicolumn{1}{c| }{\bf SQLite or MySQL
- } & \multicolumn{1}{c| }{\bf Bacula  } \\
- \hline 
-{Job Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Media Record  } & {Yes  } & {Yes  } \\
- \hline 
-{FileName Record  } & {Yes  } & {No  } \\
- \hline 
-{File Record  } & {Yes  } & {No  } \\
- \hline 
-{FileSet Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Pool Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Client Record  } & {Yes  } & {Yes  } \\
- \hline 
-{JobMedia Record  } & {Yes  } & {Yes  } \\
- \hline 
-{List Job Records  } & {Yes  } & {Yes  } \\
- \hline 
-{List Media Records  } & {Yes  } & {Yes  } \\
- \hline 
-{List Pool Records  } & {Yes  } & {Yes  } \\
- \hline 
-{List JobMedia Records } & {Yes  } & {Yes  } \\
- \hline 
-{Delete Pool Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Delete Media Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Update Pool Record  } & {Yes  } & {Yes  } \\
- \hline 
-{Implement Verify  } & {Yes  } & {No  } \\
- \hline 
-{MD5 Signatures  } & {Yes  } & {No }
-\\ \hline 
+versions of Bacula and install them into separate directories.
 
-\end{longtable}
+%\addcontentsline{lot}{table}{SQLite vs MySQL Database Comparison}
+\LTXtable{0.95\linewidth}{table_sqlitevsmysql}
 
 In addition, since there is no SQL available, the Console commands: {\bf
 sqlquery}, {\bf query}, {\bf retention}, and any other command that directly
-uses SQL are not available with the Internal database. 
+uses SQL are not available with the Internal database.