Public bug reported:
mar...@thekorn ~/devel/zeitgeist/trunk % grep -ri iso_strptime.py .
./COPYRIGHT:26:File zeitgeist/loggers/iso_strptime.py is part of wadllib, which
is
./extra/packaging/debian/copyright:20:Files: zeitgeist/loggers/iso_strptime.py
From my understanding
Public bug reported:
We have a bunch of queries which are using no index and therefor are
much slower than others, this is one example:
Running: engine.find_eventids(TimeRange.always(), [], StorageState.Any, 6,
ResultType.MostRecentSubjects)
DEBUG:zeitgeist.sql:Got query:
QUERY:
SELECT
Bug 673394 describes anopther class of slow queries
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework:
** Changed in: unity
Status: New = Triaged
** Changed in: unity
Importance: Undecided = Low
** Also affects: unity-place-files
Importance: Undecided
Status: New
** Changed in: unity-place-files
Importance: Undecided = Low
** Changed in: unity-place-files
Status:
** Changed in: unity
Status: New = Triaged
** Changed in: unity
Importance: Undecided = Low
** Also affects: unity-place-files
Importance: Undecided
Status: New
** Changed in: unity-place-files
Importance: Undecided = Low
** Changed in: unity-place-files
Status:
Also, bug 673452
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Confirmed
Bug description:
THE
** Changed in: zeitgeist
Status: New = Fix Committed
--
'iso_strptime.py' is mentioned in COPYRIGHT files although we don't ship this
file anymore
https://bugs.launchpad.net/bugs/673386
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is
** Branch linked: lp:zeitgeist
--
'iso_strptime.py' is mentioned in COPYRIGHT files although we don't ship this
file anymore
https://bugs.launchpad.net/bugs/673386
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
Hello Zeitgeist Framework Team,
On 2010-11-10 10:21z (4 minutes ago), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
Hello Zeitgeist Framework Team,
On 2010-11-10 10:21z (3 minutes ago), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.5 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
Hello Zeitgeist Framework Team,
On 2010-11-10 10:21z (5 minutes ago), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
Something looks to be ascrew if an event has multiple subject? But it looks
like that was also the case before this branch..? Do we have a test for this?
Can you re-insert the comment about returning None for missing events - I think
it's nice to note there that it is our API contract.
But
Public bug reported:
Let me summarize what we have wrt subj_origin
1) we have a subj_origin column in the event table, which is an integer
pointing to an entry in the uri table
2) we have an index on the subj_origin column of the event table
3) we have subj_origin in event view, which is not
Seif Lotfy has proposed merging lp:~seif/zeitgeist/clean-up-get-events into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
I cleaned up and shortend the code
I am not sure how much performance increase we get out of that but I think its
much more compact now.
All
The test you added will pass if no events are found. While a test for template
matching with multiple subjects is also useful, what I meant for a test where
you insert and retrieve an event with 2 subjects, validating that it worked.
--
** Branch linked: lp:~thekorn/zeitgeist/faster_origin_queries
--
Using the subj_origin column of event_view is slower than it should be
https://bugs.launchpad.net/bugs/673452
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Status: New = Triaged
--
Using the subj_origin column of event_view is slower than it should be
https://bugs.launchpad.net/bugs/673452
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Status: New = Confirmed
--
Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/673394
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
foo.txt gets renamed to nice.txt, then to stuff.txt, there's a new foo.txt,
stuff.txt gets renamed to omg!!.
renames
---
old_uri | new_uri | timestamp
foo.txtomg!! 1234
nice.txt omg!! 2500
stuff.txt omg!! 5000
events with
I dont understand the soltuion tbh
However looking at your table i got an idea
Scenario:
* foo.txt gets renamed to nice.txt
* nice.txt gets renamed to stuff.txt
* create new foo.txt,
* stuff.txt gets renamed to omg!!
uri
=
id | value
---
1 | foo.txt
2 | nice.txt
3 | stuff.txt
Hello Zeitgeist Framework Team,
On 2010-11-11 01:59z (3 minutes ago), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.3 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
Hello Zeitgeist Framework Team,
On 2010-11-11 01:59z (4 minutes ago), you uploaded a translation
template for zeitgeist in Zeitgeist Framework 0.1 in Launchpad.
The template has now been imported successfully.
Thank you,
The Launchpad team
___
22 matches
Mail list logo
