Changes between Version 5 and Version 6 of TracSqlHelperScript


Ignore:
Timestamp:
Jun 6, 2018, 6:12:06 AM (15 months ago)
Author:
figaro
Comment:

Moved example to description

Legend:

Unmodified
Added
Removed
Modified
  • TracSqlHelperScript

    v5 v6  
    77While there is considerable contention on the subject, I am one of those people that doesn't like to see SQL statements in Python code (or C code, etc). I especially don't like it when the same basic statements are repeated all over the place. So TracSqlHelperScript is my attempt to encapsulate all of this logic in one place. These are functions I've already co-written for the TracHoursPlugin and then rewritten (some of them) for the GeoTicketPlugin. Instead of rewriting them again for yet another plugin where I want this functionality, I'm making a library out of them which hopefully I will backport to those plugins.
    88
    9 I'd really like a better story for this in general, like having at least some of these convenient functions on the DB cursor. But quite frankly, I'm not an SQL expert, and IMHO it would be better for Trac to completely abstract its backend, so I'll leave whatever action for those that know better and stick with this library for my purposes.
     9I'd really like a better story for this in general, like having at least some of these convenient functions on the database cursor. But quite frankly, I'm not an SQL expert, and IMHO it would be better for Trac to completely abstract its backend, so I'll leave whatever action for those that know better and stick with this library for my purposes.
     10
     11See the GeoTicketPlugin and the TracHoursPlugin for how these functions are used. Essentially, they are to help build new plugins with when you want to have a slightly abstracted database layer. I'd love help with this, if anyone would like to contribute.
    1012
    1113== Bugs/Feature Requests
     
    2729You can check out TracSqlHelperScript from [/svn/tracsqlhelperscript here] using Subversion, or [source:tracsqlhelperscript browse the source] with Trac.
    2830
    29 == Example
     31== Installation
    3032
    31 See the GeoTicketPlugin and the TracHoursPlugin for how these functions are used. Essentially, they are to help build new plugins with when you want to have a slightly abstracted database layer. I'd love help with this, if anyone would like to contribute.
     33General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    3234
    3335== Recent Changes