> On Tue, May 25, 2010 at 2:58 AM, Cooke, Mark
> wrote:
> >>
> >> On Thu, May 20, 2010 at 9:22 AM, Chris Nelson
> >> wrote:
> >> > Celso Providelo wrote:
> >> >> ...
> >> >>> I was briefly excited when I saw this note because I've
> >> been trying
> >> >>> all the Gantt chart plugins looking f
On Tue, May 25, 2010 at 2:58 AM, Cooke, Mark wrote:
>>
>> On Thu, May 20, 2010 at 9:22 AM, Chris Nelson
>> wrote:
>> > Celso Providelo wrote:
>> >> ...
>> >>> I was briefly excited when I saw this note because I've
>> been trying
>> >>> all the Gantt chart plugins looking for one that works and i
> Then I look to Postgres
Then (getting this back around to a technical discussion), I have to ask:
How the heck do I grant permissions on the DATABASE so that any newly
created tables automatically inherit said permissions? I ended up just
granting permissions on each table in the database, be
> To add relevant content, I switched from sqlite3 to mysql on a test
> instance just to make sure I wasn't being naive about performance. I
> wasn't. Sqlite performed as well as mysql for our low-concurrency
> workload.
I don't think anyone ever claimed that going to MySQL/PostgreSQL over
Sqli
* On 25 May 2010, Noah Kantrowitz wrote:
>
> This is starting to drift off-topic, but the rapid departure of many of the
> prominent FOSS people from Sun has me worried. Most have left very suddenly,
> ...
Ah, that is good information and something I put stock in.
> on MySQL?". There is no rea
> -Original Message-
> From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com]
> On Behalf Of David Champion
> Sent: Tuesday, May 25, 2010 2:27 PM
> To: trac-users@googlegroups.com
> Subject: Re: [Trac] Backend dB choice
>
> * On 25 May 2010, Ma
* On 25 May 2010, Matt Caron wrote:
> Noah Kantrowitz wrote:
> > And for comparison, reasons to avoid MySQL:
> >
>
> > Much ambiguity about the future of the project since the Oracle takeover.
>
> Theoretically, one should be able to use MariaDB, though I have not
> tested this.
>
> But y
Noah Kantrowitz wrote:
> And for comparison, reasons to avoid MySQL:
>
> Much ambiguity about the future of the project since the Oracle takeover.
Theoretically, one should be able to use MariaDB, though I have not
tested this.
But yes, I share your fears as to what SnOracle will do...
--
Noah Kantrowitz wrote:
> The biggest problem with SQLite is that it has a very simple locking
> model. More or less, if someone is writing to the DB no one else can
> touch it.
This. Once we got to about 20 people using it, someone would run a long
query and it would lock everyone out with "
le, but if you
have more than a dozen people using a Trac site full-time it can get
annoying.
--Noah
From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com] On
Behalf Of Itamar O
Sent: Tuesday, May 25, 2010 12:20 PM
To: trac-users@googlegroups.com
Subject: Re: [Trac] Backend
tt Caron
> *Sent:* Tuesday, May 25, 2010 5:57 AM
> *To:* trac-users@googlegroups.com
> *Subject:* Re: [Trac] Backend dB choice
>
>
>
> > Sorry to hijack but I was just wondering if you have any specific
> > reasons for choosing mysql over e.g. PostgreSQL. I don't
Matt Caron
Sent: Tuesday, May 25, 2010 5:57 AM
To: trac-users@googlegroups.com
Subject: Re: [Trac] Backend dB choice
> Sorry to hijack but I was just wondering if you have any specific
> reasons for choosing mysql over e.g. PostgreSQL. I don't know that
> much about dBs really s
> Sorry to hijack but I was just wondering if you have any specific
> reasons for choosing mysql over e.g. PostgreSQL. I don't know that
> much about dBs really so any thoughts welcome. I picked PostgreSQL
> as it seemed the better supported in Trac...
As did I. However, I wish I hadn't. My reas
>
> On Thu, May 20, 2010 at 9:22 AM, Chris Nelson
> wrote:
> > Celso Providelo wrote:
> >> ...
> >>> I was briefly excited when I saw this note because I've
> been trying
> >>> all the Gantt chart plugins looking for one that works and is
> >>> supported. However, when I saw which one you were
14 matches
Mail list logo
