From 24ef2d9e8d6b5873333b92597d41e7a28c51b0d3 Mon Sep 17 00:00:00 2001
From: Sheppy <jupiterfisch@web.de>
Date: Thu, 23 Feb 2017 12:13:05 +0100
Subject: [PATCH] small changes

---
 IDB/braindump_SS16/Makefile                               | 4 ++--
 .../{Braindump_SS16.tex => klausur_idb_SS16.tex}          | 8 +++-----
 2 files changed, 5 insertions(+), 7 deletions(-)
 rename IDB/braindump_SS16/{Braindump_SS16.tex => klausur_idb_SS16.tex} (99%)

diff --git a/IDB/braindump_SS16/Makefile b/IDB/braindump_SS16/Makefile
index f9210b1..d1bcf3e 100644
--- a/IDB/braindump_SS16/Makefile
+++ b/IDB/braindump_SS16/Makefile
@@ -1,7 +1,7 @@
-all: Braindump_SS16.pdf solutions
+all: klausur_idb_SS16.pdf solutions
 
 solutions: 
-	@pdflatex --jobname=Braindump_SS16_ML "\def\withsolutions{1} \input{Braindump_SS16.tex}"
+	@pdflatex --jobname=klausur_idb_SS16_ML "\def\withsolutions{1} \input{klausur_idb_SS16.tex}"
 
 continuous: $(PDF).continuous
 
diff --git a/IDB/braindump_SS16/Braindump_SS16.tex b/IDB/braindump_SS16/klausur_idb_SS16.tex
similarity index 99%
rename from IDB/braindump_SS16/Braindump_SS16.tex
rename to IDB/braindump_SS16/klausur_idb_SS16.tex
index fbc71b4..e7cbe90 100644
--- a/IDB/braindump_SS16/Braindump_SS16.tex
+++ b/IDB/braindump_SS16/klausur_idb_SS16.tex
@@ -375,7 +375,7 @@ x & x  & x  & 0
 .
 \end{lstlisting}
 \solution{
-\lstinputlisting{tree1.ascii}
+\lstinputlisting{tree1-sol.ascii}
 }
 \textbf{c)} Loesche aus dem folgenden B-Baum den Schluessel 10. Zwischenschritte sind nicht noetig.\\\\
 \solswitch{\lstinputlisting{tree2.ascii}}{
@@ -519,10 +519,8 @@ Eher nicht, weil jede versuchte SQL Injection am Integer.parseInt() zerschellt.
 \vspace{2.5cm}
 \textbf{b)} Wie kann man das obrige Program SICHER gegen SQL-Injections schuetzen?
 \solution{
-\begin{lstlisting}[language=java]
-preparedStmt.setInt(1, a)
-preparedStmt.execute();
-\end{lstlisting}
+preparedStmt.setInt(1, ai) \\
+preparedStmt.execute(); \\
 Aber alleine die Aussage Prepared-Statements empfinde ich hier als wichtig.
 }
 \end{document}