File: changelog

package info (click to toggle)
beancounter 0.5.1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 220 kB
  • ctags: 130
  • sloc: perl: 1,606; sh: 565; makefile: 82
file content (248 lines) | stat: -rw-r--r-- 9,279 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
beancounter (0.5.1) unstable; urgency=low

  * setup_beancounter: Fill beancounter table with current version number 
    and current date right after the table is created. 
  * debian/rules: Making sure $version is updated in beancounter, 
    update_beancounter and setup_beancounter

 -- Dirk Eddelbuettel <edd@debian.org>  Sun, 10 Mar 2002 19:38:57 -0600

beancounter (0.5.0) unstable; urgency=low

  * New release with the following new features:

    - New command 'retracement' to calculate drawdowns for the given data
      period -- these are defined as price decreases relative to the
      maximum price in the period. This can be seen as hypothetical
      unrealized losses relative to the would-coulda-shouda optimal selling
      price. Shorts are treated the other way relative to their lows.
   
    - New command 'advancement' which does the same for gains relative to lows.
  
    - Applied patch by Peter Kim <pykim@gte.net> so that 'update' now
      batches queries in round lots of one hundred symbols.
   
    - The backpopulate command is now idempotent too: it can now be run 
      even if data already exists and will use either 'insert' or 'update'
      as required.
  
    - The stockinfo table has a new column 'active' allowing to flag 
      inactive stocks (or e.g. expired options) with a 'false' value.
  
    - The database has a new table 'beancounter' with fields for the
      current version (to ensure code and database schema match) and
      the most recent update.
  
  * Detailed changes

    - BeanCounter.pm: Applied Peter's patch, pluse comments / indents

    - BeanCounter.pm: New function GetRetracementData

    - BeanCounter.pm: New function UpdateTimestamp

    - beancounter: New function portfolio_retracement
  
    - BeanCounter.pm: Rewrote DatabaseHistoricalData for idempotency
 
    - beancounter: Example now uses full example with purchase date / time
  
    - BeanCounter.pm: Rewrote SQL restriction for getting price data
  
    - Database scheme: New field 'active' to flag inactive stocks / options
  
    - BeanCounter.pm: Make use of 'active' field when retrieving data
  
    - BeanCounter.pm: Simpliefied API for ExistsDailyData()
  
    - setup_beancounter: Added creation of active field in stockinfo
  
    - update_beancounter: Idem
  
  * debian/control: Spelling correction (Closes: #124442)
  * debian/control: Upgraded to Standards-Version 3.5.0
 
 -- Dirk Eddelbuettel <edd@debian.org>  Tue,  5 Mar 2002 22:06:51 -0600

beancounter (0.4.0) unstable; urgency=low

  * New release with the following new features

    - Support for MySQL has been added: beancounter can now work with both
      PostgreSQL and MySQL, including all steps up from the database creation

    - The update command's SQL query has been rewritten so that all stocks
      known to beancounter are updated, yet still allows the use of the
      --restriction option to specify only subsets of the portfolio

    - The update command is now idempotent: it can now be run several
      times during a trading day; the initial data set will be 'insert'ed,
      following ones 'update'd (this comes at the cost of an additional query)

    - Better support of old, expired or delisted stocks: unparseable
      dates, as well as dates that "too old" (where the current default 5
      business days) are set to N/A; and dates which test for N/A are neither
      scrubbed nor databased during the "update" command.
  
    - Database backend and database name can now be set as parameters which
      facilitates multiple databases and backends to be used in parallel
  
    - New (boolean) option --fxupdate which defauls to 'true', hence the
      use of --nofxupdate prevents any updates to the FX database

    - Database scheme change in stockprices table: column names changed to
      day_open, day_close, day_change for consistency (and MySQL gripes).
      Similarly, index becomes stockindex in the indices table. Hence, 
      users /upgrading from an older version/ must run update_beancounter.
  
  * Detailed changes:

    - [BeanCounter.pm] --verbose and --debug now passed to DBI connection
      for Warn and PrintError, respectively 

    - [BeanCounter.pm] New configuration options dbsystem and dbname,
      defaulting to PostgreSQL and beancounter

    - [BeanCounter.pm] Protect name with dbh->quote for DatabaseInfoData

    - [BeanCounter.pm] DatabaseUpdate has new SQL query with sub-select

    - [BeanCounter.pm] Several small code cleanups and documentation updates
  
    - [beancounter] New command-line options --dbsystem and --dbname
  
    - [beancounter] Several updates and extensions to the pod documentation

    - [setup_beancounter] Now with command-line options -m, -s dbname, -s

    - [setup_beancounter] Parallel code for MySQL db creations added

    - [setup_beancounter] Added manual page as POD document within

    - [update_beancounter] Added code for the database table transition

    - [update_beancounter] Added manual page as POD document within
  
 -- Dirk Eddelbuettel <edd@debian.org>  Sun, 14 Oct 2001 20:57:05 -0500

beancounter (0.3.1) unstable; urgency=low

  * Bug fix release:

    - rewrote SQL queries using '--restriction arg' to allow for multiple
      portfolio restrictions to be imposed (BeanCounter.pm)

    - reflect change at Yahoo! Europe and convert quotes from ';' field
      seperator and ',' decimal point (BeanCounter.pm: GetQuote)

    - ensure that day_end_report is relative to previous day (beancounter)

    - add dbh->commit() after database updates (beancounter: add_index,
      add_portfolio; BeanCounter.pm: delete_stock)

  * Some other minor changes:

    - annualise returns if stock held > 1 year (beancounter: display_status)

    - make some functions more compact with selectcol_arrayref (BeanCounter.pm)

    - use dropdb(1) to delete database (requires PostgreSQL 7.*) (beancounter)

    - add warning if correlation non computable (BeanCounter.pm: GetRiskData)

    - add warning if date not parseable (BeanCounter: ParseDailyData)

    - add historica price retrieval for (US) mutual funds 
      (BeanCounter.pm: GetHistoricalData)

   - if data inconsistent, adjust close to to previous_close plus change
      (BeanCounter: SrubDailyData)
  
 -- Dirk Eddelbuettel <edd@debian.org>  Mon, 13 Aug 2001 21:53:18 -0500

beancounter (0.3.0) unstable; urgency=low

  * New release with the following code changes

    - new command "risk" for report with value-at-risk at (VaR) percentile
      estimates, using both the standard (parametric) approach as well as
      a nonparametric quantile estimate
      "risk" also computes marginal value-at-risk (slow for large portfolios)
      "risk" requires the Statistics::Descriptive modules

    - new option "--forceupdate <date>" to permit overriding of a faulty
      date supplied by Yahoo! Finance (which is becoming more common)

    - new command "allreports" for dayend, status and risk reports all in once

    - added status and risk reports to jobs ran by "dailyjob" command

    - new ScrubDailyData routine; currently only using the "--forceupdate
      date" check on the pricing date supplied by Yahoo!

    - prevdate defaults to "six months ago" (better default for risk report)

    - "status" also shows cash holding from table `cash' (preliminary feature)

    - improved internal logic for argument and option checking + db connection

    - improved report calculations, report display and documentation

    - documentation corrected (command is 'delete', not 'deletestock')
  
 -- Dirk Eddelbuettel <edd@debian.org>  Thu, 29 Mar 2001 19:18:54 -0600

beancounter (0.2.1) unstable; urgency=low

  * Bug fix release:

    - setup_beancounter: change last fromdate,todate to prevate,date

    - setup_beancounter: use NT, not NT.TO, to avoid FX in demo

    - beancounter: Use psql, not destroydb or dropdb, to delete db

    - debian/control: Also depend on libdbd-pg-perl (Closes: #85363)

 -- Dirk Eddelbuettel <edd@debian.org>  Fri,  9 Feb 2001 22:45:54 -0600
  
beancounter (0.2.0) unstable; urgency=low

  * New release with the following code changes

    - new table columns 'owner' and 'holder' for portfolio allow
      to differentiate between different accounts and users

    - SQL restrictions can be imposed for finer-grained analysis

    - new status command for portfolio return and holding overview

    - extrafx argument allows to specify additional currencies to
      be downloaded and stored by the 'update' command

    - date and prevdate default to today and yesterday

    - fromdate and todate options replaced by consistent use
      of prevdate and date

    - more documentation

    - data display layout changed
  
 -- Dirk Eddelbuettel <edd@debian.org>  Sat,  2 Dec 2000 17:27:48 -0600

beancounter (0.1.1) unstable; urgency=low

  * Bugfix release:
    - BeanCounter.pm: corrected minor typo in DatabaseInfoData
    - debian/rules: don't create beancounter.1 -- Makefile.PL does that too

 -- Dirk Eddelbuettel <edd@debian.org>  Tue, 25 Jul 2000 22:47:40 -0400

beancounter (0.1.0) unstable; urgency=low

  * Initial Debian (and upstream) release.

 -- Dirk Eddelbuettel <edd@debian.org>  Sun, 23 Jul 2000 22:14:17 -0400