错误跟踪架构
我正在寻求实现我自己的错误跟踪数据库。有人可以向我指出现有的许多跟踪数据库中的任何一个的数据库表布局图吗？我已经提出了我的大部分要求，而且大部分都很简单，但我想了解其他人认为重要的内容以及他们如何准确地实现某些目标。
I'm looking to implement my own bug tracking database. Could somebody point me to the database table layout diagrams of any of the many tracking databases already in existance. I've come up with most of my requirements, and its simple for the most part, but I want to get an idea of what other people thought was important and how exactly they accomplished certain objectives.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
FogBugz 能够让您以 MySQL 或 SQL Server 格式导出错误数据库。然后，您可以查看导出并了解数据的结构。
我确信应用程序中会缺少内置的表格，但这将为您提供一个起点。
另一种选择是简单地查看大量 OSS 错误跟踪选项的代码，看看它们是如何做到的。 Trac 和 Bugzilla 将是一个很好的起点。
（天哪，简单地安装其中任何一个并使用 PHPMyAdmin 之类的东西查看数据库结构可能会花费一个小时，并且应该为您提供一个很好的起点）
FogBugz has the ability to let you export your bug database in a MySQL or SQL Server format. You could then look at the export and see how the data is structured.
I'm sure there will be missing tables that are built in to the app, but this will give you a starting point.
The other option would be to simply go look at the code for the numerous OSS bug tracking options out there and see how they do it. Trac and Bugzilla would be a good place to start.
(hell, simply installing either of those and looking at the DB structure with something like PHPMyAdmin would probably take all of an hour and should give you a great place to start)