On Tue, Jul 23, 2013 at 4:13 PM, Hua Xiang <[email protected]> wrote:
> 2013/7/23 Joachim Dreimann <[email protected]> > > > On 23 July 2013 15:58, Hua Xiang <[email protected]> wrote: > > > > > > > > > > > Hi Gary, > > > > > >> I can't see the attachment you mentioned so it is probably removed. > > >> Otherwise, that error on the svn info command at least tells us that > the > > >> copy of the code in /home/xiang/bep_0008_time_series_reports was > checked > > >> out with an older version of svn than you are attempting to svn info > at > > >> this point. Your previous response suggested that tortoisesvn is using > > >> subversion 1.7.10 so that ties together at least. > > >> > > > Here is the snapshot. > > > > > > [image: 内嵌图片 1] > > > > > > > All attachments are stripped from your email before it gets distributed > to > > the dev@ list, so we can't see the snapshot. > > > > > > > > > > If you are happy to continue using the command line (and/or you want > to > > > upgrade your tortoisesvn to 1.8) you could follow the advice of the > error > > > message: > > > > > >> svn upgrade /home/xiang/bep_0008_time_series_reports > > >> > > >> I would expect the svn info command to work assuming that is > successful. > > >> > > > Ok. I will do upgrade. > > > > > > > > >> Meanwhile, it is not so clear to me whether you attempted a fresh > > >> checkout of the bep_0008_time_series_reports branch.. perhaps the > > removed > > >> attachment would have told me that though > > >> > > > > > > Yes, I did a fresh checkout of the branch. > > > BTW, I have created SQL statements to generate reports locally (my > local > > > sqlite). I would like to know how to commit my SQL statements to the > > > repository so that other developer can see my change? > > > > > > > I'd be keen to hear other opinions on this again, but you can probably > just > > post plain SQL statements to a pastebin service, for example > > http://pastebin.com/, and share links to them on this list. > > > > I will put the SQL statements in > bep_0008_time_series_reports\trac\trac\db_default.py That's fine for now, but please be aware that you'll need to structure your code in a plugin before we can consider integrating it into Bloodhound. For examples, take a look at how `bloodhound_multiproduct` , `bloodhound_relations` and the other plugins are structured. With few exceptions, the code for your plugin will be entirely contained in a directory with a name like `bloodhound_time_series_reports`.
