On Wednesday 10 February 2010 02:33:39 pm Kern Sibbald wrote:
> On Wednesday 10 February 2010 20:18:22 Andreas Piesk wrote:
> > Hi list,
> >
> > while testing things using bat 5.0.0 i found one more sql which doesn't
> > work with sqlite3, please see bacula-sql.patch (contains all non-working
> > s
On Wednesday 10 February 2010 21:41:36 Andreas Piesk wrote:
> Kern Sibbald schrieb:
> > Thanks for your patch. I will apply the parts that apply to bat. It is
> > really too bad that SQLite3 has this bug. However, the solution is OK
> > and does no harm and is a good way to work around their bug.
Kern Sibbald schrieb:
>
> Thanks for your patch. I will apply the parts that apply to bat. It is
> really
> too bad that SQLite3 has this bug. However, the solution is OK and does no
> harm and is a good way to work around their bug.
>
> If you have a few minutes, it might be worthwhile to f
On 02/10/10 14:18, Andreas Piesk wrote:
> Hi list,
>
> while testing things using bat 5.0.0 i found one more sql which doesn't work
> with sqlite3, please
> see bacula-sql.patch (contains all non-working statements i've found so far).
> would changing all 'USING ()' to 'ON ()' break things?
>
>
On Wednesday 10 February 2010 20:18:22 Andreas Piesk wrote:
> Hi list,
>
> while testing things using bat 5.0.0 i found one more sql which doesn't
> work with sqlite3, please see bacula-sql.patch (contains all non-working
> statements i've found so far). would changing all 'USING ()' to 'ON ()'
> b
Hi list,
while testing things using bat 5.0.0 i found one more sql which doesn't work
with sqlite3, please
see bacula-sql.patch (contains all non-working statements i've found so far).
would changing all 'USING ()' to 'ON ()' break things?
i think i've asked some time ago, why bat has to be run
