-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The blast_sequence table is big and only getting bigger #288
Comments
I try to use postgres schema to access blast_sequence table but encounter the permission issue |
ERROR: permission denied for relation blast_sequence |
I went through three script yesterday to figure out the procedure for replacing current fasta-view by blast+ application.
|
1.Encounter the issue |
There are three python package that can use for CLI:
The way than can used by javascript:
|
Get Javascript and Python get communicate using Json
|
Alright, so for sending data from the client (JavaScript) to the backend (your Django app) you need to employ something called Ajax, it stands for Asynchronous JavaScript and XML. Basically what it does is allowing you to communicate with your backend services without the need of having to reload the page, which, you would have to do using a normal POST or PUT form submission. The easiest implementation is using jQuery. jQuery is first and foremost a DOM manipulation library but since its inception has grown to encompass much more than that. example code : |
so far we need three steps to achieve the goal
|
For future reference. This is in branch "blastdbcmd" |
different path between blast/views.py and media/blast/db (where the BLAST DATABASE is) |
I've been getting warnings about the blast.sequence table growing large, and on looking at the table definitions, it seems like this is because records are never deleted when the blast database the record refers to is also deleted.
Right now this one table id around 935 MB. I did some basic tests and it looks like queries on this table may take a significant amount of time to return results.
I think the only reason we have this is for displaying the subject sequence in the results page. This functionality should be reproducible either using the included BLAST+ tools.
The text was updated successfully, but these errors were encountered: