285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
|
The same result could be obtained from Git, but because the data is
in a key/value store, much more procedural code has to be written to
walk the data and compute the result. And since that is a lot more
work, the question is seldom asked.
The ease of querying Fossil data using SQL means that status or
history information about the project under management is easier
to obtain. And being easier means that it is more likely to happen.
Fossil reports tend to be more detailed and useful.
Consider the [/timeline?c=6df7a853ec16865b|this Fossil timeline]
compared to its
[https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34|its
closest equivalent in GitHub]. Judge for yourself: Which of those
reports is more useful to a developer trying to understand what happened?
The bottom line is that even though Fossil and Git are built around
the same low-level data structure, the use of SQL
to query this data makes the data more accessible in Fossil, resulting
in more detailed information being available to the user. This
improves situational awareness and makes working on the project
|
|
|
|
|
|
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
|
The same result could be obtained from Git, but because the data is
in a key/value store, much more procedural code has to be written to
walk the data and compute the result. And since that is a lot more
work, the question is seldom asked.
The ease of querying Fossil data using SQL means that status or
history information about the project under management is easier
to obtain. Being easier means that it is more likely to happen.
Fossil reports tend to be more detailed and useful.
Consider the [/timeline?c=6df7a853ec16865b|this Fossil timeline]
compared to
[https://github.com/drhsqlite/fossil-mirror/commits/master?after=f720c106d297ca1f61bccb30c5c191b88a626d01+34 |
its closest equivalent in GitHub]. Judge for yourself: Which of those
reports is more useful to a developer trying to understand what happened?
The bottom line is that even though Fossil and Git are built around
the same low-level data structure, the use of SQL
to query this data makes the data more accessible in Fossil, resulting
in more detailed information being available to the user. This
improves situational awareness and makes working on the project
|