Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread Dmitri Maziuk 

On 8/12/2014 7:00 PM, Ryan Ollos wrote:


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.


Might be worth looking into sqlalchemy for the next development cycle...

Dima


--
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread W. Martin Borgert 

Quoting Dmitri Maziuk dmaz...@bmrb.wisc.edu:

Might be worth looking into sqlalchemy for the next development cycle...


An ORM in Trac? That would be to good to be true!

(I remember, that there were discussions about using an ORM before, and
that there was a lot of resistance. I don't recall, why that was.)

--
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread Ryan Ollos 
On Wed, Aug 13, 2014 at 7:52 AM, Dmitri Maziuk dmaz...@bmrb.wisc.edu
wrote:

 On 8/12/2014 7:00 PM, Ryan Ollos wrote:

  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.


 Might be worth looking into sqlalchemy for the next development cycle...

 Dima


Just to be clear, there is not any problem with Trac and it's database API.
The issue is that developers don't follow the guidelines for database API
usage to make their plugins cross-db compatible. Further, most developers
only test with SQLite.
http://trac.edgewall.org/wiki/TracDev/DatabaseApi#RulesforDBAPIUsage

The ORM could make it less likely that developers make errors when writing
database access code, but that would remain to be seen and depend on
implementation details.

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread Dimitri Maziuk 
On 08/13/2014 10:08 AM, Ryan Ollos wrote:

 Just to be clear, there is not any problem with Trac and it's database API.
 The issue is that developers don't follow the guidelines for database API
 usage to make their plugins cross-db compatible.

IME being cross-compatible is a major PITA even when I am the only
developer. Paramstyle is one of the more obvious examples.

 The ORM could make it less likely that developers make errors when writing
 database access code, but that would remain to be seen and depend on
 implementation details.

Sqlalchemy has the core layer that provides an engine-agnostic sql
wrapper -- arguably ugly, possibly less efficient, but it's there.

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread Dimitri Maziuk 

 Sqlalchemy has the core layer that provides an engine-agnostic sql
 wrapper -- arguably ugly, possibly less efficient, but it's there.

That is, you don't have to use the ORM layer if you don't need to, you
can just use the core.

(sorry to f'up on my own post)
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-13 Thread Jared Bownds 
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 hof...@web.de 
 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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-12 Thread Jared Bownds 
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?

On Wednesday, August 6, 2014 1:01:30 PM UTC-7, RjOllos wrote:

 On Wed, Aug 6, 2014 at 9:35 AM, Jared Bownds jared@gmail.com 
 javascript: wrote:

 Hi everyone, 

 I'm reaching out for advise on how to handle recent errors that have come 
 up since attempting to migrate from SQLite to PostgreSQL.

 First has to do with the sub-tickets plugin.  Since upgrading, no tickets 
 can be accessed due to the error outlined below.

  How to Reproduce 

 While doing a GET operation on `/ticket/1790`, Trac issued an internal 
 error.

 ''(please provide additional details here)''

 Request parameters:
 {{{
 {'id': u'1790'}
 }}}

 User agent: `Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 
 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36`

  System Information 
 || '''`Trac`''' || `1.0` ||
 || '''`Trac`''' || `1.0` ||
 || '''`Babel`''' || `0.9.6` ||
 || '''`Genshi`''' || `0.6 (without speedups)` ||
 || '''`GIT`''' || `1.7.1` ||
 || '''`mod_wsgi`''' || `3.2 (WSGIProcessGroup trac-dev 
 WSGIApplicationGroup trac-dev.agraquest.int|)` ||
 || '''`psycopg2`''' || `2.0.13` ||
 || '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]] 
 `[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
 || '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]] 
 `[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
 || '''`pytz`''' || `2010h` ||
 || '''`pytz`''' || `2010h` ||
 || '''`setuptools`''' || `0.6c11` ||
 || '''`setuptools`''' || `0.6c11` ||
 || '''`Subversion`''' || `1.6.15 (r1038135)` ||
 || '''`jQuery`''' || `1.7.2` ||

  Enabled Plugins 
 || '''`AutocompleteUsers`''' || `0.4.2dev` ||
 || '''`BlackMagicTicketTweaks`''' || `0.12r1` ||
 || '''`BreadCrumbsNav`''' || `0.2` ||
 || '''`ComponentDependencyPlugin`''' || `0.1` ||
 || '''`ContextChrome`''' || `0.3` ||
 || '''`graphviz`''' || `0.7.7dev` ||
 || '''`ReadonlySignedTickets`''' || `N/A` ||
 || '''`ScreenshotPaste`''' || `0.1.1` ||
 || '''`TicketSidebarProvider`''' || `0.0` ||
 || '''`TicketValidator`''' || `0.2dev` ||
 || '''`trac-MultiRepoSearchPlugin`''' || `0.6` ||
 || '''`trac-WorkflowNotificationPlugin`''' || `0.5` ||
 || '''`TracAccountManager`''' || `0.4.3` ||
 || '''`TracAnnouncer`''' || `1.0dev` ||
 || '''`TracAttachmentNotifyPlugin`''' || `1.0.1` ||
 || '''`TracAutoWikify`''' || `0.2dev` ||
 || '''`TracCustomFieldAdmin`''' || `0.2.8-r12166` ||
 || '''`TracDateField`''' || `2.0.0dev-r12118` ||
 || '''`TracDragDrop`''' || `0.12.0.11` ||
 || '''`TracHoursPlugin`''' || `0.6.0dev` ||
 || '''`TracHtmlNotificationPlugin`''' || `0.12.0.1` ||
 || '''`TracMigratePlugin`''' || `0.12.0.3` ||
 || '''`TracReportManager`''' || `0.1` ||
 || '''`TracSubTicketsPlugin`''' || `0.2.0.dev-20130908` ||

  Python Traceback 
 {{{
 Traceback (most recent call last):
   File 
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
 line 497, in _dispatch_request
 dispatcher.dispatch(req)
   File 
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
 line 224, in dispatch
 self._post_process_request(req, *resp)
   File 
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
 line 338, in _post_process_request
 resp = f.post_process_request(req, *resp)
   File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 73, 
 in post_process_request
 children = self.get_children(ticket.id)
   File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 107, 
 in get_children
 (parent_id, ))
   File 
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/db/util.py, line 
 65, in execute
 return self.cursor.execute(sql_escape_percent(sql), args)
 ProgrammingError: relation subtickets does not exist
 LINE 1: SELECT parent, child FROM subtickets WHERE parent=1790
   ^

 }}}


 Check if there is a table subtickets in the database, and if not, then 
 something went wrong in your migration.

 Why did you decide to migrate to PostgreSQL?
  


-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-12 Thread Steffen Hoffmann 
-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
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlPqdAMACgkQ31DJeiZFuHc5JACcCQ9bLKES5wo9FHSQeb+nw2aq
UFAAoMiYYy0sstUvJFoybwqztFsGGBeR
=V1IV
-END PGP SIGNATURE-

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-12 Thread Ryan Ollos 
On Tue, Aug 12, 2014 at 1:07 PM, Steffen Hoffmann hoff...@web.de 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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-07 Thread Greg Troxel 

For what it's worth, I have been running several trac instances with
postgresql (on NetBSD) starting around late 2007.  Generally things have
been fine, and occasionally updating to a newer postgresql version has
exposed bugs in trac's SQL code, typically type sloppiness.

I have not tried subtickets, though.   We are using mastertickets but
using the blocked-by relation to mean subtickets, usually.



pgphs9mddJ9hW.pgp
Description: PGP signature

[Trac] Re: PostgreSQL - a straw poll

2014-08-06 Thread Jared Bownds 
Hi everyone, 

I'm reaching out for advise on how to handle recent errors that have come 
up since attempting to migrate from SQLite to PostgreSQL.

First has to do with the sub-tickets plugin.  Since upgrading, no tickets 
can be accessed due to the error outlined below.

 How to Reproduce 

While doing a GET operation on `/ticket/1790`, Trac issued an internal 
error.

''(please provide additional details here)''

Request parameters:
{{{
{'id': u'1790'}
}}}

User agent: `Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, 
like Gecko) Chrome/36.0.1985.125 Safari/537.36`

 System Information 
|| '''`Trac`''' || `1.0` ||
|| '''`Trac`''' || `1.0` ||
|| '''`Babel`''' || `0.9.6` ||
|| '''`Genshi`''' || `0.6 (without speedups)` ||
|| '''`GIT`''' || `1.7.1` ||
|| '''`mod_wsgi`''' || `3.2 (WSGIProcessGroup trac-dev WSGIApplicationGroup 
trac-dev.agraquest.int|)` ||
|| '''`psycopg2`''' || `2.0.13` ||
|| '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]] 
`[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
|| '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]] 
`[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
|| '''`pytz`''' || `2010h` ||
|| '''`pytz`''' || `2010h` ||
|| '''`setuptools`''' || `0.6c11` ||
|| '''`setuptools`''' || `0.6c11` ||
|| '''`Subversion`''' || `1.6.15 (r1038135)` ||
|| '''`jQuery`''' || `1.7.2` ||

 Enabled Plugins 
|| '''`AutocompleteUsers`''' || `0.4.2dev` ||
|| '''`BlackMagicTicketTweaks`''' || `0.12r1` ||
|| '''`BreadCrumbsNav`''' || `0.2` ||
|| '''`ComponentDependencyPlugin`''' || `0.1` ||
|| '''`ContextChrome`''' || `0.3` ||
|| '''`graphviz`''' || `0.7.7dev` ||
|| '''`ReadonlySignedTickets`''' || `N/A` ||
|| '''`ScreenshotPaste`''' || `0.1.1` ||
|| '''`TicketSidebarProvider`''' || `0.0` ||
|| '''`TicketValidator`''' || `0.2dev` ||
|| '''`trac-MultiRepoSearchPlugin`''' || `0.6` ||
|| '''`trac-WorkflowNotificationPlugin`''' || `0.5` ||
|| '''`TracAccountManager`''' || `0.4.3` ||
|| '''`TracAnnouncer`''' || `1.0dev` ||
|| '''`TracAttachmentNotifyPlugin`''' || `1.0.1` ||
|| '''`TracAutoWikify`''' || `0.2dev` ||
|| '''`TracCustomFieldAdmin`''' || `0.2.8-r12166` ||
|| '''`TracDateField`''' || `2.0.0dev-r12118` ||
|| '''`TracDragDrop`''' || `0.12.0.11` ||
|| '''`TracHoursPlugin`''' || `0.6.0dev` ||
|| '''`TracHtmlNotificationPlugin`''' || `0.12.0.1` ||
|| '''`TracMigratePlugin`''' || `0.12.0.3` ||
|| '''`TracReportManager`''' || `0.1` ||
|| '''`TracSubTicketsPlugin`''' || `0.2.0.dev-20130908` ||

 Python Traceback 
{{{
Traceback (most recent call last):
  File 
/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
line 497, in _dispatch_request
dispatcher.dispatch(req)
  File 
/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
line 224, in dispatch
self._post_process_request(req, *resp)
  File 
/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py, 
line 338, in _post_process_request
resp = f.post_process_request(req, *resp)
  File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 73, in 
post_process_request
children = self.get_children(ticket.id)
  File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 107, 
in get_children
(parent_id, ))
  File 
/usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/db/util.py, line 
65, in execute
return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: relation subtickets does not exist
LINE 1: SELECT parent, child FROM subtickets WHERE parent=1790
  ^

}}}



On Tuesday, October 19, 2010 9:57:11 PM UTC-7, Andy Baker wrote:

 Hi All,

 I'm looking into switching from sqlite to postgreSQL as our backend. I'm 
 assuming this shouldn't be an issue, but does anyone have any good/bad 
 experiences to share?

 Ideally I'd like to hear from people using bleeding edge 0.12 saying yep, 
 works just fine :-)

 Cheers
 Andy




-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] Re: PostgreSQL - a straw poll

2014-08-06 Thread Ryan Ollos 
On Wed, Aug 6, 2014 at 9:35 AM, Jared Bownds jared.bow...@gmail.com wrote:

Hi everyone,

 I'm reaching out for advise on how to handle recent errors that have come
 up since attempting to migrate from SQLite to PostgreSQL.

 First has to do with the sub-tickets plugin.  Since upgrading, no tickets
 can be accessed due to the error outlined below.

  How to Reproduce 

 While doing a GET operation on `/ticket/1790`, Trac issued an internal
 error.

 ''(please provide additional details here)''

 Request parameters:
 {{{
 {'id': u'1790'}
 }}}

 User agent: `Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36
 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36`

  System Information 
 || '''`Trac`''' || `1.0` ||
 || '''`Trac`''' || `1.0` ||
 || '''`Babel`''' || `0.9.6` ||
 || '''`Genshi`''' || `0.6 (without speedups)` ||
 || '''`GIT`''' || `1.7.1` ||
 || '''`mod_wsgi`''' || `3.2 (WSGIProcessGroup trac-dev
 WSGIApplicationGroup trac-dev.agraquest.int|)` ||
 || '''`psycopg2`''' || `2.0.13` ||
 || '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]]
 `[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
 || '''`Python`''' || `2.6.6 (r266:84292, Apr 11 2011, 15:50:32) ` [[br]]
 `[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)]` ||
 || '''`pytz`''' || `2010h` ||
 || '''`pytz`''' || `2010h` ||
 || '''`setuptools`''' || `0.6c11` ||
 || '''`setuptools`''' || `0.6c11` ||
 || '''`Subversion`''' || `1.6.15 (r1038135)` ||
 || '''`jQuery`''' || `1.7.2` ||

  Enabled Plugins 
 || '''`AutocompleteUsers`''' || `0.4.2dev` ||
 || '''`BlackMagicTicketTweaks`''' || `0.12r1` ||
 || '''`BreadCrumbsNav`''' || `0.2` ||
 || '''`ComponentDependencyPlugin`''' || `0.1` ||
 || '''`ContextChrome`''' || `0.3` ||
 || '''`graphviz`''' || `0.7.7dev` ||
 || '''`ReadonlySignedTickets`''' || `N/A` ||
 || '''`ScreenshotPaste`''' || `0.1.1` ||
 || '''`TicketSidebarProvider`''' || `0.0` ||
 || '''`TicketValidator`''' || `0.2dev` ||
 || '''`trac-MultiRepoSearchPlugin`''' || `0.6` ||
 || '''`trac-WorkflowNotificationPlugin`''' || `0.5` ||
 || '''`TracAccountManager`''' || `0.4.3` ||
 || '''`TracAnnouncer`''' || `1.0dev` ||
 || '''`TracAttachmentNotifyPlugin`''' || `1.0.1` ||
 || '''`TracAutoWikify`''' || `0.2dev` ||
 || '''`TracCustomFieldAdmin`''' || `0.2.8-r12166` ||
 || '''`TracDateField`''' || `2.0.0dev-r12118` ||
 || '''`TracDragDrop`''' || `0.12.0.11` ||
 || '''`TracHoursPlugin`''' || `0.6.0dev` ||
 || '''`TracHtmlNotificationPlugin`''' || `0.12.0.1` ||
 || '''`TracMigratePlugin`''' || `0.12.0.3` ||
 || '''`TracReportManager`''' || `0.1` ||
 || '''`TracSubTicketsPlugin`''' || `0.2.0.dev-20130908` ||

  Python Traceback 
 {{{
 Traceback (most recent call last):
   File
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py,
 line 497, in _dispatch_request
 dispatcher.dispatch(req)
   File
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py,
 line 224, in dispatch
 self._post_process_request(req, *resp)
   File
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/web/main.py,
 line 338, in _post_process_request
 resp = f.post_process_request(req, *resp)
   File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 73,
 in post_process_request
 children = self.get_children(ticket.id)
   File build/bdist.linux-x86_64/egg/tracsubtickets/web_ui.py, line 107,
 in get_children
 (parent_id, ))
   File
 /usr/lib/python2.6/site-packages/Trac-1.0-py2.6.egg/trac/db/util.py, line
 65, in execute
 return self.cursor.execute(sql_escape_percent(sql), args)
 ProgrammingError: relation subtickets does not exist
 LINE 1: SELECT parent, child FROM subtickets WHERE parent=1790
   ^

 }}}


Check if there is a table subtickets in the database, and if not, then
something went wrong in your migration.

Why did you decide to migrate to PostgreSQL?

-- 
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 trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

[Trac] Re: PostgreSQL - a straw poll

2010-10-26 Thread Andy Baker 
Thanks everyone. Your experiences and thoughts are much appreciated.

Cheers
Andy

On 20 October 2010 05:57, Andy Baker bungy...@gmail.com wrote:

 Hi All,

 I'm looking into switching from sqlite to postgreSQL as our backend. I'm
 assuming this shouldn't be an issue, but does anyone have any good/bad
 experiences to share?

 Ideally I'd like to hear from people using bleeding edge 0.12 saying yep,
 works just fine :-)

 Cheers
 Andy




-- 
You received this message because you are subscribed to the Google Groups Trac 
Users group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.