> On Tue, 23 Jul 2019 09:23:10 -0500, Dimitri Maziuk via Bacula-users said:
>
> On 7/23/2019 6:02 AM, Martin Simmons wrote:
>
> > If this is being caused by the PathVisibility table then you could try to
> > either delete that table if it is empty or alter its schema definition to
> > use
>
On 7/23/2019 6:02 AM, Martin Simmons wrote:
If this is being caused by the PathVisibility table then you could try to
either delete that table if it is empty or alter its schema definition to use
bigint instead of int8 and integer instead of int4. (I'm assuming you are
working with a copy of the
This looks like a bug in pgloader's type parser so I don't think you fix it
with a cast.
If this is being caused by the PathVisibility table then you could try to
either delete that table if it is empty or alter its schema definition to use
bigint instead of int8 and integer instead of int4. (I'm
Finally got some time to poke at this again. pgloader looked promising, but
almost immediately I ran into problems with it not understanding some of
SQLite's types:
What I am doing here?
> At
> int8
> ^ (Line 1, Column 3, Position 3)
> In context SQLITE-TYPE-NAME:
> While parsing SQLITE-TYP
On 5/9/19 5:41 PM, David Brodbeck wrote:
> On Wed, May 1, 2019 at 3:14 PM Phil Stracchino wrote:
>> Surely you could have just bscanned the media you had?
>>
... Obviously now that
> the SQLite rug is going to be pulled out from under me I may have to
> revisit the bscan idea.
I haven't tried t
On Wed, May 1, 2019 at 3:14 PM Phil Stracchino wrote:
> On 5/1/19 5:57 PM, David Brodbeck wrote:
> > To be honest, my mistake was I didn't realize that by "testing purposes"
> > they meant "a temporary, throwaway system where you delete everything
> > before moving on to production." By the time
On 5/2/19 1:35 PM, Tilman Schmidt wrote:
> Am 02.05.2019 um 00:14 schrieb Phil Stracchino:
>> Surely you could have just bscanned the media you had?
>
> s/just/hired a few temps who'd/ :-)
Might still be cheaper than hiring one database guru to hand-edit
catalog.sql for psql. ;)
--
Dimitri Mazi
Am 02.05.2019 um 00:14 schrieb Phil Stracchino:
> Surely you could have just bscanned the media you had?
s/just/hired a few temps who'd/ :-)
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/
On 5/1/19 5:57 PM, David Brodbeck wrote:
> To be honest, my mistake was I didn't realize that by "testing purposes"
> they meant "a temporary, throwaway system where you delete everything
> before moving on to production." By the time I decided Bacula was doing
> the job for me and it was time to m
To be honest, my mistake was I didn't realize that by "testing purposes"
they meant "a temporary, throwaway system where you delete everything
before moving on to production." By the time I decided Bacula was doing the
job for me and it was time to move to a more robust backend, I had too much
back
On 5/1/19 3:47 AM, Kern Sibbald wrote:
> Aside from the work it takes to maintain the code, please be aware that if
> ever
> a SQLite database
> becomes corrupted, to the best of my knowledge there are no tools to correct
> it.
That is a valid argument, however, the fix for that is rather simpl
On Wed, May 1, 2019, at 18:23, Dan Langille wrote:
> Please move from SQLite to PostgreSQL. You will be better off.
The problem is that we are lacking a documented way to do so.
--
Tilman Schmidt
til...@imap.cc
___
Bacula-users mailing list
Bacula-us
On Wed, May 1, 2019, at 4:59 AM, Kern Sibbald wrote:
> Hello,
>
> Just so everyone knows how I feel about SQLite -- it is a great program,
> written by a very good programmer. It is probably closer to Postgres
> than to MySQL in its syntax.
An aside...
There is a reason for that similarity. W
Hello,
Just so everyone knows how I feel about SQLite -- it is a great program,
written by a very good programmer. It is probably closer to Postgres
than to MySQL in its syntax. However, it is really not an appropriate
database for many reasons for Bacula, and maintaining the update tables
scrip
Hello,
I want to second this email, and thank Sven and the others for
maintaining SQLite
in Bacula.
I will probably make one more release of 9.4.x which will have
SQLite in it, but please note that
the next version of Bacula will have a major change to
On Monday 2019-04-29 14:36:07 Dimitri Maziuk via Bacula-users wrote:
> On 4/29/19 1:57 PM, Josip Deanovic wrote:
> > Because of the reasons Kern already wrote.
>
> Yes, but they have nothing to do with the question.
It does. It implies that it is not supported by the authors/maintainers
of the Ba
On 29.04.19 20:57, Josip Deanovic wrote:
> It's not that SQLite is bad or does not have the needed capabilities
> but it simply adds to the complexity of the source and maintenance of
> bacula features.
Also besides Carsten Leonhardt and me from Debian nobody has been
testing or even maintaining
On 4/29/19 1:57 PM, Josip Deanovic wrote:
> Because of the reasons Kern already wrote.
Yes, but they have nothing to do with the question.
> It's not that SQLite is bad or does not have the needed capabilities
Precisely: back when it was supported there was nothing wrong with using
it, provided
On Monday 2019-04-29 12:01:03 Dimitri Maziuk via Bacula-users wrote:
> On 4/29/19 10:54 AM, Phil Stracchino wrote:
> > Was SQLite *ever* actually *recommended* for production?
>
> For a small dataset with a very limited number of volumes and backup
> cycles, why not?
Because of the reasons Kern a
On 4/29/19 10:54 AM, Phil Stracchino wrote:
> Was SQLite *ever* actually *recommended* for production?
For a small dataset with a very limited number of volumes and backup
cycles, why not?
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.a
On 4/29/19 11:49 AM, David Brodbeck wrote:
>
>
> On Sat, Apr 20, 2019 at 4:32 AM Gary R. Schmidt
> mailto:g...@mcleod-schmidt.id.au>> wrote:
>
> SQLite was deprecated in Bacula something of the order of ten years
> ago,
> which is about when I installed Bacula at my current $ORK.
>
On Sat, Apr 20, 2019 at 4:32 AM Gary R. Schmidt
wrote:
> SQLite was deprecated in Bacula something of the order of ten years ago,
> which is about when I installed Bacula at my current $ORK.
>
Interestingly, the 9.0.4 release notes say that sqlite has been deprecated
"for a long time," but I hav
Hello,
sob., 20 kwi 2019 o 12:33 Tilman Schmidt napisał(a):
> Hi Radosław,
>
> On Fri, Apr 19, 2019, at 11:40, Radosław Korzeniewski wrote:
>
> What "resources" are you referring to? My current phone has 64bit OS and
> 4GB of RAM (top models has 8G). Having a real bare metal server with
> hundre
David Brodbeck wrote:
I've been wondering the same thing, especially since there seems to be no
official way to migrate an SQLite database to PostgreSQL or MariaDB. I'm
actually not opposed to doing using one of those (I feel like a "real"
RDBMS might offer better performance and stability in
On 20/04/2019 20:14, Tilman Schmidt wrote:
Hi Radosław,
On Fri, Apr 19, 2019, at 11:40, Radosław Korzeniewski wrote:
What "resources" are you referring to? My current phone has 64bit OS
and 4GB of RAM (top models has 8G). Having a real bare metal server
with hundreds GB of ram is not a big dea
Hi Radosław,
On Fri, Apr 19, 2019, at 11:40, Radosław Korzeniewski wrote:
> What "resources" are you referring to? My current phone has 64bit OS and 4GB
> of RAM (top models has 8G). Having a real bare metal server with hundreds GB
> of ram is not a big deal. Storage space is extremely cheap too
Hello,
pt., 19 kwi 2019 o 13:32 Oliver Lehmann napisał(a):
> Hi Radoslaw,
>
> thanks for your mail.
>
> I would understand that if the developers say that they don't
> want to support SQLite because of the extra work it creates
> for them to support it. But this would be more or less the
> only
Hello,
The principal reason for dropping SQLite is as Radek stated -- it is
simply extra overhead that we do not need. This is particularly evident
when we have database schema changes. Doing schema changes with an
existing database can be quite complicated and prone to errors with
SQLite,
Hi Radoslaw,
thanks for your mail.
I would understand that if the developers say that they don't
want to support SQLite because of the extra work it creates
for them to support it. But this would be more or less the
only reason I could accept ;-)
SQLite is a good solution for an embedded RDBMS.
Hello,
śr., 10 kwi 2019 o 02:37 David Brodbeck napisał(a):
> I've been wondering the same thing, especially since there seems to be no
> official way to migrate an SQLite database to PostgreSQL or MariaDB. I'm
> actually not opposed to doing using one of those (I feel like a "real"
> RDBMS might
I've been wondering the same thing, especially since there seems to be no
official way to migrate an SQLite database to PostgreSQL or MariaDB. I'm
actually not opposed to doing using one of those (I feel like a "real"
RDBMS might offer better performance and stability in my case -- my
installation
Hi,
I just migrated my Bacula installation from 7 to 9.
During executing the DB schema update Tool, I noticed, that SQLite got
deprecated.
I wonder why? :(
I didn't wanted to install, maintain a full RDBMS which eats up
ressources and might contain security issues just to get my backups
32 matches
Mail list logo
