9 years agoStewart Lord committed change 18944 into Added p4aliases file to make DVCS act more like git | ||
1 comment | ||
14 years agoStewart Lord committed change 7927 into Cowbells back by popular demand. | ||
14 years agoStewart Lord committed change 7917 into Added my user conference visualizer. | ||
15 years agoStewart Lord committed change 7621 into Updated create table statements to use the IF NOT EXISTS condition. This allows SQL to be fed into an existing database without errors/warnings. | ||
15 years agoStewart Lord committed change 7620 into Minor update to Track2SQL to avoid timezone unset issue and split() function deprecated in PHP 5.3. | ||
16 years agoStewart Lord committed change 7338 into Rolled-back change 7209. This removes the endTime column from the process table. Track2SQL no longer attempts to analyze 'completed' entries. Thi...s change was influenced by three factors: - Analyzing 'completed' entries significantly degrades performance (about 2.75x slower in my tests). - In some versions of PHP (5.2.8) the strtotime() function suffers from a memory leak. - The 'completed' entries are not part of Vtrack output. « | ||
16 years agoStewart Lord committed change 7209 into Integrating an enhancement from Michael Shield's guest branch. Track2SQL now records the end time of each process (when it is reported). This informa...tion is reported for every completed process when -vserver=2|3 logging is enabled. If verbose server logging is enabled this is more reliable than start 'time' + 'lapse' because (by default) lapse is only reported when it exceeds a certain threshold. If, however, vtrack=1 is set then lapse time will be reported for every command. Note: this change brings a schema change. It adds a 'endTime' column to the process table. « | ||
16 years agoStewart Lord committed change 7199 into Updated Track2SQL readme file to reflect schema changes. | ||
16 years agoStewart Lord committed change 7198 into It is now possible to accumulate output from multiple invocations of track2sql in a single database. Previously, the processKey was a incrementing va...lue that always started at zero. Therefore, processKeys from separate runs of track2sql would collide if inserted into the same databse. Now, track2sql uses a 36 character universally unique identifier (UUID) for each process. UUIDs give us reasonable confidence that the process keys will never collide. One consequence of this change is that the schema is slightly different. The type of the processKey column is now a 36 character varchar instead of a integer. Another side-effect of this change is that the output of track2sql cannot be predicted and will always be different even when processing the same log file. Track2sql performance is largely unaffected, however, insert and select performance may degrade somewhat due to the larger key size. « | ||
16 years agoStewart Lord committed change 7197 into | ||
16 years agoStewart Lord committed change 7193 into | ||
16 years agoStewart Lord committed change 7104 into Follow-on to 7098. The quote() function now wraps and escapes the given string. | ||
16 years agoStewart Lord committed change 7098 into | ||
17 years agoStewart Lord committed change 6424 into Updated track2sql disclaimer. Addded a link to the readme file from the script itself. | ||
17 years agoStewart Lord committed change 6379 into Fixed a bug where track2sql failed to properly extract some table usage data if 'pages reordered' were reported. | ||
17 years agoStewart Lord committed change 6289 into | ||
18 years agoStewart Lord committed change 6010 into Fixed a bug where track2sql failed to properly parse lock times in 2007.2 log files. This was due to a small change in the log file format. | ||
18 years agoStewart Lord committed change 5889 into | ||
18 years agoStewart Lord committed change 5883 into Fixed minor typo in README. | ||
18 years agoStewart Lord committed change 5858 into Added disclaimer to script. | ||
18 years agoStewart Lord committed change 5857 into Initial add of track2sql to the public depot. | ||
Adjust when notifications are sent to you about reviews that you're associated with (as an author, reviewer, project member or moderator).