From 934ce26d16f00ff3df0e3c82327644295b06218f Mon Sep 17 00:00:00 2001
From: Marco van Wieringen <mvw@planets.elm.net>
Date: Thu, 27 May 2010 21:29:10 +0200
Subject: [PATCH] Removed workaround for bug in Ingres with insert into tables
 with sequences from the batch insert temporary table. Added comment to the
 Ingres make table script to document the bug numbers which should be fixed in
 the Ingres version to be able to run batch inserts and currently known patch
 numbers for Solaris x86 and Linux x86_64.

---
 bacula/src/cats/make_ingres_tables.in | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/bacula/src/cats/make_ingres_tables.in b/bacula/src/cats/make_ingres_tables.in
index 2dc8c162ae..3dd62447ca 100755
--- a/bacula/src/cats/make_ingres_tables.in
+++ b/bacula/src/cats/make_ingres_tables.in
@@ -9,6 +9,15 @@ db_user=${db_user:-@db_user@}
 
 sql -u${db_user} $* ${db_name} <<END-OF-DATA
 
+--
+-- When using batch insert make sure you adhere to the following
+-- minimum Ingres version:
+--
+-- Ingres 9.2 or higher with the fix for bug 123652 and bug 117256
+--   For Solaris x86 this is Ingres 9.2. + patch 13785 or higher
+--   For Linux x86_64 this is Ingres 9.2 + patch 13790 or higher
+--
+
 --
 -- As it seems the upper limit for a VARCHAR/VARBYTE column is 32000 bytes
 -- We could have used a BLOB as storage type which can go up to 2 Gb but
-- 
2.39.5