Documents won't open

Bug #718828 reported by Jefficus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glyphicus
Fix Released
Medium
Xiaonuo Gantan

Bug Description

In the latest code (pulled on Feb 14, 2011) I can connect to the db, I can open a project (such as Perceval 3.0), I can view documents in the navigation widget, and I can see the new Lemma Widget in place, but I cannot open documents. When I attempt to open fol161r(dip) from the nav window, nothing happens and no messages appear.

I have also tried this from the most recent stable build version that users are currently using and it works fine in that version.

Changed in glyphicus:
importance: Undecided → Medium
Revision history for this message
Xiaonuo Gantan (xiaonuogantan) wrote :

I can open any document including fol161r(dip) from the nav window. Did you run the copyLemmas.py file to update the database's tables before running the newest build?

Revision history for this message
Xiaonuo Gantan (xiaonuogantan) wrote :

The file should be copyLemmaDocs.py

Revision history for this message
Jefficus (jeff-smithicus) wrote : Re: [Bug 718828] Re: Documents won't open

Ah. I forgot all about the update script. I'll get back to you.

On Mon, Feb 14, 2011 at 3:11 PM, Nikolai Roman <email address hidden>wrote:

> I can open any document including fol161r(dip) from the nav window. Did
> you run the copyLemmas.py file to update the database's tables before
> running the newest build?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/718828
>
> Title:
> Documents won't open
>

--
Jeff Smith
Computer Science Dept.
University of Saskatchewan
Phone: 306-665-8157

Revision history for this message
Jefficus (jeff-smithicus) wrote :

Hi Nikolai. The copyLemmasDoc.py script fails, complaining that the
lemma_doc_id field does not exist. I suspect you made that change manually
and then forgot to put that table update part into the script, but I don't
want to just blindly change the db myself, in case there were other changes
you made that need to go into the script. Could you update the script and
double check that all necessary changes are in there please? Then I'll try
it again.

On Mon, Feb 14, 2011 at 3:28 PM, Jeff Smith <email address hidden> wrote:

> Ah. I forgot all about the update script. I'll get back to you.
>
>
> On Mon, Feb 14, 2011 at 3:11 PM, Nikolai Roman <email address hidden>wrote:
>
>> I can open any document including fol161r(dip) from the nav window. Did
>> you run the copyLemmas.py file to update the database's tables before
>> running the newest build?
>>
>> --
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>> https://bugs.launchpad.net/bugs/718828
>>
>> Title:
>> Documents won't open
>>
>
>
>
> --
> Jeff Smith
> Computer Science Dept.
> University of Saskatchewan
> Phone: 306-665-8157
>

--
Jeff Smith
Computer Science Dept.
University of Saskatchewan
Phone: 306-665-8157

Revision history for this message
Xiaonuo Gantan (xiaonuogantan) wrote :

Yes. That's probably the case. Could you send me your original version
of glyphicus? I think I've lost my original copy of it.

Nikolai

On Fri, Feb 18, 2011 at 8:52 AM, Jefficus <email address hidden> wrote:
> Hi Nikolai. The copyLemmasDoc.py script fails, complaining that the
> lemma_doc_id field does not exist. I suspect you made that change manually
> and then forgot to put that table update part into the script, but I don't
> want to just blindly change the db myself, in case there were other changes
> you made that need to go into the script. Could you update the script and
> double check that all necessary changes are in there please? Then I'll try
> it again.
>
> On Mon, Feb 14, 2011 at 3:28 PM, Jeff Smith <email address hidden> wrote:
>
>> Ah. I forgot all about the update script. I'll get back to you.
>>
>>
>> On Mon, Feb 14, 2011 at 3:11 PM, Nikolai Roman <email address hidden>wrote:
>>
>>> I can open any document including fol161r(dip) from the nav window. Did
>>> you run the copyLemmas.py file to update the database's tables before
>>> running the newest build?
>>>
>>> --
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>> https://bugs.launchpad.net/bugs/718828
>>>
>>> Title:
>>>  Documents won't open
>>>
>>
>>
>>
>> --
>> Jeff Smith
>> Computer Science Dept.
>> University of Saskatchewan
>> Phone: 306-665-8157
>>
>
>
> --
> Jeff Smith
> Computer Science Dept.
> University of Saskatchewan
> Phone: 306-665-8157
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/718828
>
> Title:
>  Documents won't open
>
> Status in Glyphicus Exploratory Markup Text Editor:
>  Confirmed
>
> Bug description:
>  In the latest code (pulled on Feb 14, 2011) I can connect to the db, I
>  can open a project (such as Perceval 3.0), I can view documents in the
>  navigation widget, and I can see the new Lemma Widget in place, but I
>  cannot open documents. When I attempt to open fol161r(dip) from the
>  nav window, nothing happens and no messages appear.
>
>  I have also tried this from the most recent stable build version that
>  users are currently using and it works fine in that version.
>

Revision history for this message
Jefficus (jeff-smithicus) wrote :

I'm assuming you mean a copy of the DB, and not the application. Here's a
copy of Yin's db, as it exists now, prior to any updates.

(BTW, you should get in the habit of storing a before-snapshot and an
after-snapshot of your test db to associate with each update script you
write. That makes it really easy to go back and debug your script later.
Like now. :-)

On Fri, Feb 18, 2011 at 8:52 AM, Jeff Smith <email address hidden> wrote:

> Hi Nikolai. The copyLemmasDoc.py script fails, complaining that the
> lemma_doc_id field does not exist. I suspect you made that change manually
> and then forgot to put that table update part into the script, but I don't
> want to just blindly change the db myself, in case there were other changes
> you made that need to go into the script. Could you update the script and
> double check that all necessary changes are in there please? Then I'll try
> it again.
>
>
> On Mon, Feb 14, 2011 at 3:28 PM, Jeff Smith <email address hidden> wrote:
>
>> Ah. I forgot all about the update script. I'll get back to you.
>>
>>
>> On Mon, Feb 14, 2011 at 3:11 PM, Nikolai Roman <email address hidden>wrote:
>>
>>> I can open any document including fol161r(dip) from the nav window. Did
>>> you run the copyLemmas.py file to update the database's tables before
>>> running the newest build?
>>>
>>> --
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>> https://bugs.launchpad.net/bugs/718828
>>>
>>> Title:
>>> Documents won't open
>>>
>>
>>
>>
>> --
>> Jeff Smith
>> Computer Science Dept.
>> University of Saskatchewan
>> Phone: 306-665-8157
>>
>
>
>
> --
> Jeff Smith
> Computer Science Dept.
> University of Saskatchewan
> Phone: 306-665-8157
>

--
Jeff Smith
Computer Science Dept.
University of Saskatchewan
Phone: 306-665-8157

Revision history for this message
Xiaonuo Gantan (xiaonuogantan) wrote : Re: [Bug 718828] [NEW] Documents won't open

Yeah. That's exactly what I meant. Thanks for the advice.

Nikolai

On Friday, February 18, 2011, Jefficus <email address hidden> wrote:
> I'm assuming you mean a copy of the DB, and not the application. Here's a
> copy of Yin's db, as it exists now, prior to any updates.
>
> (BTW, you should get in the habit of storing a before-snapshot and an
> after-snapshot of your test db to associate with each update script you
> write. That makes it really easy to go back and debug your script later.
> Like now. :-)
>
>
> On Fri, Feb 18, 2011 at 8:52 AM, Jeff Smith <email address hidden> wrote:
>
>> Hi Nikolai. The copyLemmasDoc.py script fails, complaining that the
>> lemma_doc_id field does not exist. I suspect you made that change manually
>> and then forgot to put that table update part into the script, but I don't
>> want to just blindly change the db myself, in case there were other changes
>> you made that need to go into the script. Could you update the script and
>> double check that all necessary changes are in there please? Then I'll try
>> it again.
>>
>>
>> On Mon, Feb 14, 2011 at 3:28 PM, Jeff Smith <email address hidden> wrote:
>>
>>> Ah. I forgot all about the update script. I'll get back to you.
>>>
>>>
>>> On Mon, Feb 14, 2011 at 3:11 PM, Nikolai Roman <email address hidden>wrote:
>>>
>>>> I can open any document including fol161r(dip) from the nav window. Did
>>>> you run the copyLemmas.py file to update the database's tables before
>>>> running the newest build?
>>>>
>>>> --
>>>> You received this bug notification because you are a direct subscriber
>>>> of the bug.
>>>> https://bugs.launchpad.net/bugs/718828
>>>>
>>>> Title:
>>>>  Documents won't open
>>>>
>>>
>>>
>>>
>>> --
>>> Jeff Smith
>>> Computer Science Dept.
>>> University of Saskatchewan
>>> Phone: 306-665-8157
>>>
>>
>>
>>
>> --
>> Jeff Smith
>> Computer Science Dept.
>> University of Saskatchewan
>> Phone: 306-665-8157
>>
>
>
> --
> Jeff Smith
> Computer Science Dept.
> University of Saskatchewan
> Phone: 306-665-8157
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/718828
>
> Title:
>  Documents won't open
>
> Status in Glyphicus Exploratory Markup Text Editor:
>  Confirmed
>
> Bug description:
>  In the latest code (pulled on Feb 14, 2011) I can connect to the db, I
>  can open a project (such as Perceval 3.0), I can view documents in the
>  navigation widget, and I can see the new Lemma Widget in place, but I
>  cannot open documents. When I attempt to open fol161r(dip) from the
>  nav window, nothing happens and no messages appear.
>
>  I have also tried this from the most recent stable build version that
>  users are currently using and it works fine in that version.
>

Revision history for this message
Xiaonuo Gantan (xiaonuogantan) wrote :

I've pushed revision 50 up to the repository which contains a modified copyLemmaDocs.py which could be run from the command line:
$ python copyLemmaDocs.py -m 'hostname' -u 'username' -p 'password' -d 'database name'

If the column 'lemma_doc_id' already exists in the 'words' table, the user will be asked whether to continue the update. If it doesn't exist, it will be added to the 'words' table.

I tried the new copyLemmaDocs.py and I can open any document without problems.

Changed in glyphicus:
status: Confirmed → Fix Committed
Changed in glyphicus:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.