Last 7 days

• Dec 13, 2009

  issue 78 (Option to choose length of Hit summary) changed by daevaorn   -  

  Status: Invalid

  Owner: daevaorn

  Status: Invalid

  Owner: daevaorn
• Dec 13, 2009

  issue 100 (Djapian fails to index when stemming lang is "multi") Labels changed by daevaorn   -  

  Labels: Milestone-Release2.3

  Labels: Milestone-Release2.3
• Dec 13, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) changed by daevaorn   -   Ok. I think this issue is not the Djapian authority.

  Status: WontFix

  Owner: daevaorn

  Ok. I think this issue is not the Djapian authority.

  Status: WontFix

  Owner: daevaorn
• Dec 13, 2009

  issue 93 (creating and registering indexers using a class decorator) Labels changed by daevaorn   -  

  Labels: Type-Enhancement −Type-Defect

  Labels: Type-Enhancement −Type-Defect
• Dec 13, 2009

  issue 89 (result set cannot be stored in session) Status changed by daevaorn   -  

  Status: Invalid

  Status: Invalid
• Dec 13, 2009

  issue 100 (Djapian fails to index when stemming lang is "multi") changed by daevaorn   -  

  Status: Accepted

  Owner: daevaorn

  Status: Accepted

  Owner: daevaorn
• Dec 12, 2009

  issue 100 (Djapian fails to index when stemming lang is "multi") commented on by arkanus   -   forget to tell i'm using the lastest svn revision

  forget to tell i'm using the lastest svn revision
• Dec 12, 2009

  issue 100 (Djapian fails to index when stemming lang is "multi") reported by arkanus   -   When trying to run "management.py index --rebuild" when DJAPIAN_STEMMING_LANG = "multi" the command fails. It appears that djapian should be intercepting the "Multi" but is not doing it and pass it to xapian. here is the full traceback. Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/usr/lib/pymodules/python2.6/django/core/management/__init__.py", line 362, in execute_manager utility.execute() File "/usr/lib/pymodules/python2.6/django/core/management/__init__.py", line 303, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 222, in execute output = self.handle(*args, **options) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/management/commands/ index.py", line 165, in handle rebuild(verbose, per_page, commit_each) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/management/commands/ index.py", line 130, in rebuild indexer.update(None, after_index, per_page, commit_each) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/indexer.py", line 235, in update generator.set_stemmer(xapian.Stem(stem_lang)) File "/usr/lib/python2.6/dist-packages/xapian.py", line 4026, in __init__ _xapian.Stem_swiginit(self,_xapian.new_Stem(*args)) xapian.InvalidArgumentError: Language code multi unknown

  When trying to run "management.py index --rebuild" when DJAPIAN_STEMMING_LANG = "multi" the command fails. It appears that djapian should be intercepting the "Multi" but is not doing it and pass it to xapian. here is the full traceback. Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/usr/lib/pymodules/python2.6/django/core/management/__init__.py", line 362, in execute_manager utility.execute() File "/usr/lib/pymodules/python2.6/django/core/management/__init__.py", line 303, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/pymodules/python2.6/django/core/management/base.py", line 222, in execute output = self.handle(*args, **options) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/management/commands/ index.py", line 165, in handle rebuild(verbose, per_page, commit_each) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/management/commands/ index.py", line 130, in rebuild indexer.update(None, after_index, per_page, commit_each) File "/home/arkanus/Codigo/django_tests/djapian_test/djapian/indexer.py", line 235, in update generator.set_stemmer(xapian.Stem(stem_lang)) File "/usr/lib/python2.6/dist-packages/xapian.py", line 4026, in __init__ _xapian.Stem_swiginit(self,_xapian.new_Stem(*args)) xapian.InvalidArgumentError: Language code multi unknown

Last 30 days

• Dec 11, 2009

  Installation (Installation guide) Wiki page commented on by sidmitra.del   -   Xapian binary for Windows users http://www.flax.co.uk/xapian_windows.shtml

  Xapian binary for Windows users http://www.flax.co.uk/xapian_windows.shtml
• Dec 08, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) commented on by m...@braxmeier.de   -   May be this is an idea? From http://trac.edgewall.org/ticket/8575 ... We add a update_sequence method to the db backend classes, which is much like the get_last_id method. The plugins would be responsible for calling it, but at least there would be a db independent method for it.

  May be this is an idea? From http://trac.edgewall.org/ticket/8575 ... We add a update_sequence method to the db backend classes, which is much like the get_last_id method. The plugins would be responsible for calling it, but at least there would be a db independent method for it.
• Dec 06, 2009

  Tutorial (Tutorial for applying Djapian on example application) Wiki page edited by daevaorn   -   Revision r323 Edited wiki page through web user interface.

  Revision r323 Edited wiki page through web user interface.
• Dec 05, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) commented on by daevaorn   -   Oh, this is intersting! How do you think can Djapian do something to prevent such error conditions?

  Oh, this is intersting! How do you think can Djapian do something to prevent such error conditions?
• Dec 05, 2009

  issue 99 (License terms should be documented better) Status changed by daevaorn   -   Fixed with r320

  Status: Fixed

  Fixed with r320

  Status: Fixed
• Dec 05, 2009

  ChangesInVersion020301 (2.3.1 version release notes) Wiki page edited by daevaorn   -   Revision r322 Added notes about LICENSE file

  Revision r322 Added notes about LICENSE file
• Dec 05, 2009

  r321 (Backported LICENSE file from trunk ) committed by daevaorn   -   Backported LICENSE file from trunk

  Backported LICENSE file from trunk
• Dec 05, 2009

  r320 (Fixed #99 - added LICENSE file. ) committed by daevaorn   -   Fixed #99 - added LICENSE file.

  Fixed #99 - added LICENSE file.
• Dec 05, 2009

  ChangesInVersion020301 (2.3.1 version release notes) Wiki page added by daevaorn   -   Revision r319 Added draft notes for 2.3.1 release

  Revision r319 Added draft notes for 2.3.1 release
• Dec 05, 2009

  r318 (backported index operation fixes ) committed by daevaorn   -   backported index operation fixes

  backported index operation fixes
• Dec 05, 2009

  r317 (2.3 branch creation ) committed by daevaorn   -   2.3 branch creation

  2.3 branch creation
• Dec 05, 2009

  issue 98 (manage.py index doesn't work (for me)) Status changed by daevaorn   -   Fixed with r314, r315, r316. Jonas, thanks again!

  Status: Fixed

  Fixed with r314, r315, r316. Jonas, thanks again!

  Status: Fixed
• Dec 05, 2009

  r316 (Added transaction commit at the end of index process iterati...) committed by daevaorn   -   Added transaction commit at the end of index process iteration

  Added transaction commit at the end of index process iteration
• Dec 05, 2009

  r315 (Fixed action lookup; update -> edit ) committed by daevaorn   -   Fixed action lookup; update -> edit

  Fixed action lookup; update -> edit
• Dec 05, 2009

  r314 (Fixed counter reset ) committed by daevaorn   -   Fixed counter reset

  Fixed counter reset
• Dec 05, 2009

  issue 99 (License terms should be documented better) changed by daevaorn   -  

  Status: Accepted

  Owner: daevaorn

  Labels: Priority-High Milestone-Release2.3 −Priority-Medium

  Status: Accepted

  Owner: daevaorn

  Labels: Priority-High Milestone-Release2.3 −Priority-Medium
• Dec 05, 2009

  issue 98 (manage.py index doesn't work (for me)) commented on by hguerreiro   -   The patch is OK, it worked like a charm. Thanks!

  The patch is OK, it worked like a charm. Thanks!
• Dec 05, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) commented on by m...@braxmeier.de   -   Hi daevaorn, Now we found a solution. The problem arises using postgres together with djapian. The problem was a sequence out of sync with its automatically incremented field data (http://docs.djangoproject.com/en/dev/ref/django-admin/ -> django-admin.py sqlsequencereset) Regards, Hans

  Hi daevaorn, Now we found a solution. The problem arises using postgres together with djapian. The problem was a sequence out of sync with its automatically incremented field data (http://docs.djangoproject.com/en/dev/ref/django-admin/ -> django-admin.py sqlsequencereset) Regards, Hans
• Dec 04, 2009

  Tutorial (Tutorial for applying Djapian on example application) Wiki page commented on by prestonhunt   -   Executing a query from the indexshell without a maximum number of entries to return results in a ValueError on v2.3. Also quotes are needed if there is a space. I think this is correct syntax: >>> query "death star" 10

  Executing a query from the indexshell without a maximum number of entries to return results in a ValueError on v2.3. Also quotes are needed if there is a space. I think this is correct syntax: >>> query "death star" 10
• Dec 04, 2009

  issue 99 (License terms should be documented better) reported by uptimebox   -   I try to package Djapian for debian. Debian policy explicitly requires reference to upstream licence. But nither source code nor related files contain license information. The only place license is referenced if PKG- INFO file, but I'm not sure if it is relieble source of information. Suggestion: source tree should contain LICENSE file.

  I try to package Djapian for debian. Debian policy explicitly requires reference to upstream licence. But nither source code nor related files contain license information. The only place license is referenced if PKG- INFO file, but I'm not sure if it is relieble source of information. Suggestion: source tree should contain LICENSE file.
• Dec 04, 2009

  issue 98 (manage.py index doesn't work (for me)) commented on by marcosmoyano   -   jonasnockert, Your patch worked beautifully :-) Thanks a lot! Marcos

  jonasnockert, Your patch worked beautifully :-) Thanks a lot! Marcos
• Dec 03, 2009

  issue 98 (manage.py index doesn't work (for me)) Labels changed by daevaorn   -  

  Labels: Priority-High Milestone-Release2.3 −Priority-Medium

  Labels: Priority-High Milestone-Release2.3 −Priority-Medium
• Dec 03, 2009

  issue 98 (manage.py index doesn't work (for me)) commented on by jonasnockert   -   I've created a patch for this issue. I would actually say it's three separate issues though: 1. With 2.3, the the transaction.commit() added per #26 was removed but the @transaction.commit_manually decorator was left. This means that the function will throw an exception if changes aren't properly committed. That's what @hguerreiro encountered. I've added back the transaction.commit() line because that will commit any changes left uncommited before exiting the function. This line can be removed when all changes are always committed. 2. Since the transaction.commit() was removed, issue #26 should have been re-opened. With 2.3, running Djapian daemonized does not work propely as changes are not caught. This issue is solved by the transaction.commit() line. However, when all changes are always committed, one could choose to run this line only when there are no changes. 3. There is no 'update' action. This is the reason @marcosmoyano keeps getting the "There are N objects to update" over and over again. When there are 'delete' or 'add' actions, he runs into issue 1 above. I changed 'update' to 'edit'. If you could add Djapian 2.2.4 to Pypi, I would be most grateful. I'm using Djapian with Buildout and 2.2.4 worked fine for me but I can't define "Djapian==2.2.4" as a dependency anymore. Now I can only get 2.3, which is not working for me. Actually, please leave old versions of Djapian on Pypi if you don't have to remove them. It makes defining specific versions of Djapian as a dependency much easier. Thanks!

  I've created a patch for this issue. I would actually say it's three separate issues though: 1. With 2.3, the the transaction.commit() added per #26 was removed but the @transaction.commit_manually decorator was left. This means that the function will throw an exception if changes aren't properly committed. That's what @hguerreiro encountered. I've added back the transaction.commit() line because that will commit any changes left uncommited before exiting the function. This line can be removed when all changes are always committed. 2. Since the transaction.commit() was removed, issue #26 should have been re-opened. With 2.3, running Djapian daemonized does not work propely as changes are not caught. This issue is solved by the transaction.commit() line. However, when all changes are always committed, one could choose to run this line only when there are no changes. 3. There is no 'update' action. This is the reason @marcosmoyano keeps getting the "There are N objects to update" over and over again. When there are 'delete' or 'add' actions, he runs into issue 1 above. I changed 'update' to 'edit'. If you could add Djapian 2.2.4 to Pypi, I would be most grateful. I'm using Djapian with Buildout and 2.2.4 worked fine for me but I can't define "Djapian==2.2.4" as a dependency anymore. Now I can only get 2.3, which is not working for me. Actually, please leave old versions of Djapian on Pypi if you don't have to remove them. It makes defining specific versions of Djapian as a dependency much easier. Thanks!
• Nov 27, 2009

  issue 98 (manage.py index doesn't work (for me)) commented on by hguerreiro   -   I have the same problem: * djapian (2.3) * django (trunk), * postgresql (8.4) * python-psycopg2 * Debian testing My traceback is: $ ./manage.py index --commit_each --verbose --per_page=1 There are 8770 objects to update .Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/home/helder/python_local/django/core/management/__init__.py", line 439, in execute_manager utility.execute() File "/home/helder/python_local/django/core/management/__init__.py", line 380, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/helder/python_local/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/home/helder/python_local/django/core/management/base.py", line 222, in execute output = self.handle(*args, **options) File "/arquivo/www/busca/newsrss/local/djapian/management/commands/index.py", line 153, in handle update_changes(verbose, timeout, not make_daemon, per_page, commit_each) File "/home/helder/python_local/django/db/transaction.py", line 267, in _commit_manually leave_transaction_management() File "/home/helder/python_local/django/db/transaction.py", line 77, in leave_transaction_management raise TransactionManagementError("Transaction managed block ended with pending COMMIT/ROLLBACK") django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK When I try to do a MyModel.indexer.update() it seems that it tries to index all the documents (this takes about an hour, so after a while I interrupt this process). Helder

  I have the same problem: * djapian (2.3) * django (trunk), * postgresql (8.4) * python-psycopg2 * Debian testing My traceback is: $ ./manage.py index --commit_each --verbose --per_page=1 There are 8770 objects to update .Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/home/helder/python_local/django/core/management/__init__.py", line 439, in execute_manager utility.execute() File "/home/helder/python_local/django/core/management/__init__.py", line 380, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/helder/python_local/django/core/management/base.py", line 195, in run_from_argv self.execute(*args, **options.__dict__) File "/home/helder/python_local/django/core/management/base.py", line 222, in execute output = self.handle(*args, **options) File "/arquivo/www/busca/newsrss/local/djapian/management/commands/index.py", line 153, in handle update_changes(verbose, timeout, not make_daemon, per_page, commit_each) File "/home/helder/python_local/django/db/transaction.py", line 267, in _commit_manually leave_transaction_management() File "/home/helder/python_local/django/db/transaction.py", line 77, in leave_transaction_management raise TransactionManagementError("Transaction managed block ended with pending COMMIT/ROLLBACK") django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK When I try to do a MyModel.indexer.update() it seems that it tries to index all the documents (this takes about an hour, so after a while I interrupt this process). Helder
• Nov 26, 2009

  IndexerClass (Description of each parameter of `Indexer` class) Wiki page commented on by daevaorn   -   It will be improved as soon as posible.

  It will be improved as soon as posible.
• Nov 26, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) commented on by m...@braxmeier.de   -   Hi daevaorn, Thanks for your answer... I'm sorry, but I could not reconstruct the "sometimes" cases. We have a running webpages and every day while readers visit our pages we receive this error. Is there an option to deactivate the autoupdate function? For us it would be sufficient to update the database once a day... Thx, Hans

  Hi daevaorn, Thanks for your answer... I'm sorry, but I could not reconstruct the "sometimes" cases. We have a running webpages and every day while readers visit our pages we receive this error. Is there an option to deactivate the autoupdate function? For us it would be sufficient to update the database once a day... Thx, Hans
• Nov 24, 2009

  issue 98 (manage.py index doesn't work (for me)) changed by daevaorn   -  

  Status: Accepted

  Owner: daevaorn

  Status: Accepted

  Owner: daevaorn
• Nov 24, 2009

  issue 98 (manage.py index doesn't work (for me)) commented on by marcosmoyano   -   I forgot to mention that I've tried this on two diferent linux distributions. Arch and Ubuntu server. Both with the same results.

  I forgot to mention that I've tried this on two diferent linux distributions. Arch and Ubuntu server. Both with the same results.
• Nov 24, 2009

  issue 98 (manage.py index doesn't work (for me)) reported by marcosmoyano   -   Here's my situation. I've installed djapian (2.3) with django (1.1), postgresql (8.3) and python-psycopg2 and everything works as expected. I've created my indexers, rebuild the index, and so on. Everything works except when I try to update the index. When I run "manage.py index --verbose" one of 2 things happen. 1.- I get a nice display saying: "There are N objects to update". But nothing happens. The index doesn't get updated. or 2.- I get an error: django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK. Can someone please let me know how to work around this? Also, I can update the indexes doing something like this: from app.models import MyModel from common.indexes import MyModelIndex MyModel.indexer.update() After doing something like that I can search the changes I've made, but "manage.py index" keeps saying there are objects to be changed. Any help would be much appreciate. FYI: I have python-xapian 1.0.7 and xapian-tools 1.0.7 Marcos

  Here's my situation. I've installed djapian (2.3) with django (1.1), postgresql (8.3) and python-psycopg2 and everything works as expected. I've created my indexers, rebuild the index, and so on. Everything works except when I try to update the index. When I run "manage.py index --verbose" one of 2 things happen. 1.- I get a nice display saying: "There are N objects to update". But nothing happens. The index doesn't get updated. or 2.- I get an error: django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK. Can someone please let me know how to work around this? Also, I can update the indexes doing something like this: from app.models import MyModel from common.indexes import MyModelIndex MyModel.indexer.update() After doing something like that I can search the changes I've made, but "manage.py index" keeps saying there are objects to be changed. Any help would be much appreciate. FYI: I have python-xapian 1.0.7 and xapian-tools 1.0.7 Marcos
• Nov 23, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) commented on by daevaorn   -   To explore more precisely this issue I need concrete information about "sometimes" cases.

  To explore more precisely this issue I need concrete information about "sometimes" cases.
• Nov 23, 2009

  IndexerClass (Description of each parameter of `Indexer` class) Wiki page commented on by ivixor   -   Any chance this doc could be improved? More clarity/examples around prefixed fields would be handy!

  Any chance this doc could be improved? More clarity/examples around prefixed fields would be handy!
• Nov 23, 2009

  issue 97 (IntegrityError: duplicate key value violates unique constrai...) reported by m...@braxmeier.de   -   Has anyone any ideas? In our project we are using django with postgresql and receive "sometimes" the following error: IntegrityError: duplicate key value violates unique constraint "djapian_change_content_type_id_key" Is it possible to deactivate the "autoupdate" functionality? Or how can we solve this problem? Here our traceback: File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 410, in save self.save_base(force_insert=force_insert, force_update=force_update) File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 506, in save_base created=(not record_exists), raw=raw) File "/usr/local/lib/python2.6/dist-packages/django/dispatch/dispatcher.py", line 166, in send response = receiver(signal=self, sender=sender, **named) File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/signals.py", line 8, in post_save Change.objects.create(object=instance, action= created and "add" or "edit") File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/models.py", line 32, in create old_change.save() File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/models.py", line 65, in save super(Change, self).save() File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 410, in save self.save_base(force_insert=force_insert, force_update=force_update) File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 495, in save_base result = manager._insert(values, return_id=update_pk) File "/usr/local/lib/python2.6/dist-packages/django/db/models/manager.py", line 177, in _insert return insert_query(self.model, values, **kwargs) File "/usr/local/lib/python2.6/dist-packages/django/db/models/query.py", line 1087, in insert_query return query.execute_sql(return_id) File "/usr/local/lib/python2.6/dist-packages/django/db/models/sql/subqueries.py", line 320, in execute_sql cursor = super(InsertQuery, self).execute_sql(None) File "/usr/local/lib/python2.6/dist-packages/django/db/models/sql/query.py", line 2369, in execute_sql cursor.execute(sql, params) Thanks, Hans

  Has anyone any ideas? In our project we are using django with postgresql and receive "sometimes" the following error: IntegrityError: duplicate key value violates unique constraint "djapian_change_content_type_id_key" Is it possible to deactivate the "autoupdate" functionality? Or how can we solve this problem? Here our traceback: File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 410, in save self.save_base(force_insert=force_insert, force_update=force_update) File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 506, in save_base created=(not record_exists), raw=raw) File "/usr/local/lib/python2.6/dist-packages/django/dispatch/dispatcher.py", line 166, in send response = receiver(signal=self, sender=sender, **named) File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/signals.py", line 8, in post_save Change.objects.create(object=instance, action= created and "add" or "edit") File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/models.py", line 32, in create old_change.save() File "/usr/local/lib/python2.6/dist-packages/Djapian-2.3-py2.6.egg/djapian/models.py", line 65, in save super(Change, self).save() File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 410, in save self.save_base(force_insert=force_insert, force_update=force_update) File "/usr/local/lib/python2.6/dist-packages/django/db/models/base.py", line 495, in save_base result = manager._insert(values, return_id=update_pk) File "/usr/local/lib/python2.6/dist-packages/django/db/models/manager.py", line 177, in _insert return insert_query(self.model, values, **kwargs) File "/usr/local/lib/python2.6/dist-packages/django/db/models/query.py", line 1087, in insert_query return query.execute_sql(return_id) File "/usr/local/lib/python2.6/dist-packages/django/db/models/sql/subqueries.py", line 320, in execute_sql cursor = super(InsertQuery, self).execute_sql(None) File "/usr/local/lib/python2.6/dist-packages/django/db/models/sql/query.py", line 2369, in execute_sql cursor.execute(sql, params) Thanks, Hans
• Nov 19, 2009

  Tutorial (Tutorial for applying Djapian on example application) Wiki page commented on by sk...@carthage.edu   -   if you are using apache2 and mod_wsgi or mod_python, there is a bug in certain versions of xapian that makes apache hang ("deadlock", as they call it) when using Djapian. here is the relevant ticket with a fix for both mod_wsgi and mod_python if your version of Xapian is older than 1.0.13. http://trac.xapian.org/ticket/185

  if you are using apache2 and mod_wsgi or mod_python, there is a bug in certain versions of xapian that makes apache hang ("deadlock", as they call it) when using Djapian. here is the relevant ticket with a fix for both mod_wsgi and mod_python if your version of Xapian is older than 1.0.13. http://trac.xapian.org/ticket/185
• Nov 19, 2009

  Tutorial (Tutorial for applying Djapian on example application) Wiki page commented on by sk...@carthage.edu   -   has anyone been able to integrate this with apache2 and mod_wsgi? everything works for me from command line: from myapp.models import Event import djapian djapian.load_indexes() indexer = Event.indexer query='boo' results = indexer.search(query).prefetch() for r in results: print r but when i run it from a view that is served up by apache, the browser just hangs, no response, just the "loading" icon. i read else where that there is a problem with Xapian and mod_python, but i am using mod_wsgi. any thoughts?

  has anyone been able to integrate this with apache2 and mod_wsgi? everything works for me from command line: from myapp.models import Event import djapian djapian.load_indexes() indexer = Event.indexer query='boo' results = indexer.search(query).prefetch() for r in results: print r but when i run it from a view that is served up by apache, the browser just hangs, no response, just the "loading" icon. i read else where that there is a problem with Xapian and mod_python, but i am using mod_wsgi. any thoughts?

Earlier this year

• Nov 14, 2009

  issue 94 (Filter using foreign keys) changed by daevaorn   -   Result set provides filtering only over fields that exist in index& If you want to filter search results with foreign key field - just store it in index with specific tag and filter against it.

  Status: WontFix

  Owner: daevaorn

  Result set provides filtering only over fields that exist in index& If you want to filter search results with foreign key field - just store it in index with specific tag and filter against it.

  Status: WontFix

  Owner: daevaorn
• Nov 14, 2009

  issue 96 (python manage.py index) changed by daevaorn   -  

  Status: Invalid

  Owner: daevaorn

  Status: Invalid

  Owner: daevaorn
• Nov 14, 2009

  issue 95 (Exception Type: KeyError) Status changed by daevaorn   -  

  Status: Invalid

  Status: Invalid
• Nov 13, 2009

  issue 96 (python manage.py index) commented on by m...@braxmeier.de   -   Hi again, I posted the solution already: We changed the model, but did not update the djapian_change table. So if anyone get's the error above then first delete the djapian_change table, execute the command ./manage.py syncdb and at last rebuild the index with the command ./manage.py index --rebuild Regards, Hans

  Hi again, I posted the solution already: We changed the model, but did not update the djapian_change table. So if anyone get's the error above then first delete the djapian_change table, execute the command ./manage.py syncdb and at last rebuild the index with the command ./manage.py index --rebuild Regards, Hans
• Nov 13, 2009

  issue 95 (Exception Type: KeyError) commented on by m...@braxmeier.de   -   Hi daevaorn, Thanks for your reply. I think I found the explanation for our key error: We changed our model, but did not update the djapian_change table. So if anyone get's an KeyError or can't execute the command ./manage.py index then first delete the djapian_change table, execute the command ./manage.py syncdb and at last rebuild the index with the command ./manage.py index --rebuild Regards, Hans

  Hi daevaorn, Thanks for your reply. I think I found the explanation for our key error: We changed our model, but did not update the djapian_change table. So if anyone get's an KeyError or can't execute the command ./manage.py index then first delete the djapian_change table, execute the command ./manage.py syncdb and at last rebuild the index with the command ./manage.py index --rebuild Regards, Hans
• Nov 13, 2009

  issue 96 (python manage.py index) commented on by daevaorn   -   Does it happens just after the start of execution or after some time?

  Does it happens just after the start of execution or after some time?
• Nov 13, 2009

  issue 96 (python manage.py index) reported by m...@braxmeier.de   -   I'm using postgres. The command python manage.py index causes the following error: File "/usr/local/lib/python2.6/dist-packages/django/db/transaction.py", line 77, in leave_transaction_management raise TransactionManagementError("Transaction managed block ended with pending COMMIT/ROLLBACK") django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK Any ideas? Thx, Hans

  I'm using postgres. The command python manage.py index causes the following error: File "/usr/local/lib/python2.6/dist-packages/django/db/transaction.py", line 77, in leave_transaction_management raise TransactionManagementError("Transaction managed block ended with pending COMMIT/ROLLBACK") django.db.transaction.TransactionManagementError: Transaction managed block ended with pending COMMIT/ROLLBACK Any ideas? Thx, Hans
• Nov 13, 2009

  issue 95 (Exception Type: KeyError) changed by daevaorn   -   Please provide full traceback, source code snippet and indexer definition. It will help to solve problem.

  Status: Accepted

  Owner: daevaorn

  Please provide full traceback, source code snippet and indexer definition. It will help to solve problem.

  Status: Accepted

  Owner: daevaorn