Sound advise, thanks for pointing out the big picture.

On Tuesday, August 12, 2014 5:00:54 PM UTC-7, RjOllos wrote:
>
> On Tue, Aug 12, 2014 at 1:07 PM, Steffen Hoffmann <[email protected] 
> <javascript:>> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 12.08.2014 19:11, Jared Bownds wrote:
>> > After checking the postgres DB after the migration, there is no
>> > table called subtickets. Perhaps the migration script is not
>> > equipped to include this type of table?
>>
>> I've had a quick look at TracMigratePlugin. Its unlikely that it
>> misses specific tables as it is designed to copy ALL tables.
>>
>> Unless there was an error on migration, as Ryan already suggested.
>> Another look, this time at TracSubticketsPlugin source confirms, that
>> the plugin i.e. provides integer version numbers from
>> tracsubtickets/db_default.py for writing to Trac db table system (see
>> tracsubtickets/api.py), but that table is defined with text columns.
>> So type sloppiness is a likely cause of the TracSubticketsPlugin
>> upgrade failure that you shall see on migration.
>>
>> Steffen Hoffmann
>>
>
> That is an interesting find.
>
> I would emphasize again to Jared, unless you have a good reason to migrate 
> to PostgreSQL, you are much better off sticking with SQLite. You will find 
> fewer problems with plugins when using SQLite. I would go as far as to say, 
> if you plan to utilize dozens of plugins and you can't fix issues that 
> you'll experience with PostgreSQL on your own, you should stick with 
> SQLite. You may find yourself waiting around for others to fix things, 
> which in some cases may never happen. Many of the plugins don't have a 
> maintainer at the moment.
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to