JediVCS中的vcslog表用于什么？(What is the vcslog table in JediVCS used for?)

JediVCS中的vcslog表用于什么？(What is the vcslog table in JediVCS used for?)

只是想知道在JediVCS中使用了什么vcslog表。

我在这个表上收到了一些包含错误（在我的备份过程中，这些错误被数据库后端标记）并且修复后有可能丢失了一些数据。

如果表只是作为日志，那么这应该没问题。

其他一些信息：

本来要问JediVCS新闻组这个问题，但似乎已经失败了

我确实有最近的备份，我可以恢复但不愿意，因为它意味着找到并重新提交任何干预工作。

我将所有其他表及其数据在VCS的预修复版本和修复后版本之间进行了区分，并且它们都匹配。

我试图区分vcslog表，但我已经崩溃的工具因为表有数百万条记录。 （我认为该工具在内存中运行差异）

任何信息赞赏。

彼得梅斯

Just wondering what the vcslog table is used for in JediVCS.

I received some consistancy errors on this table (during my backup procedure these errors were flagged by the database backend) and there is a chance that after repair some data went missing.

If the table is just acting as a log then this should be ok.

Some other info:

Was going to ask this quesion on the JediVCS news group but it appears to be down

I do have recent backups that I could restore but would rather not as it means finding and re-committing any intervening work.

I diffed all other tables and their data between the pre-fix and post-fix versions of the VCS and they all match.

I tried to diff the vcslog table but the tool I have crashed as the table has millions of records. (I think the tool ran out of memory doing the diff)

Any info appreciated.

Peter Mayes

最满意答案

我最终直接邮寄了活跃的JediVCS管理员。

感谢他们的快速和帮助建议。

基本上，vcslog表包含与用户采取的操作有关的信息。 因此，它的数据完全是可选的，但建议使用。

最不实用的记录在数据库中标记为type = g。 （这记录了用户的“获取”操作）。

在数据库中直接删除这些记录后，vcslog表的大小减小了97％。 （我怀疑大量的“获取”日志是由于我们的高速自动装置）。

数据库自清楚以来一直稳定。 （大约六周前）

以下是我所指出的JediVCS帮助手册中的其他一些主题。 以防他们证明对某人有帮助。 这些详细说明了JediVCS客户端内的日志记录行为：

“项目历史” “应用服务器选项” “写VCS日志”

I ended up mailing the active JediVCS admin staff directly.

Thanks go to them for their prompt and helpul advice.

Basically the vcslog table holds information relating to actions taken by a user. As such its data is entirely optional, but recommended.

The least useful records are marked as type=g in the database. (This logs a 'get' operation by a user).

After deleting these records directly in the database the vcslog table reduced in size by 97%. (I suspect the large number of 'get' logs is due to our nighly autobuilds).

The database has been stable since the clear. (Some six weeks ago)

Here are some other topics in the JediVCS help manual I was pointed at. Just in case they prove helpful to someone. These detail the logging behaviour inside the JediVCS client:

"Project history" "Application server options" "Write VCS log"