Closed GoogleCodeExporter closed 9 years ago
Original comment by david.ba...@gmail.com
on 28 Sep 2012 at 4:05
Hi,
I have started looking at this issue, but unfortunately I am unable to
reproduce the error using just the steps you describe. I notice that you
reported using build 526 of BioLink. Build 538 is the version currently
available in the downloads area. Would you be able to download and install this
version and see if this error still occurs? Other information that may be
useful in diagnosing the problem would include whether or not your database was
an old BioLink database (Version 2.x or earlier), or if it was created since
the release of 3.0 using the starter database.
Cheers, David.
Original comment by david.ba...@gmail.com
on 28 Sep 2012 at 4:21
Also relevant may be the version of SQL Server that you are using as well.
Cheers, David.
Original comment by david.ba...@gmail.com
on 28 Sep 2012 at 4:27
[deleted comment]
[deleted comment]
Hi David,
Data were imported from BioLink 2. Updating to Build 538 and running
scriptBiolink_V2_5_0_Scripts.sql seemed to fix this problem. However, the
script did not run error free:
Erors when running Biolink_V2_5_0_Scripts.sql
[27%] Adding/Updating vwBiotaAssociateText...
Msg 208, Level 16, State 1, Procedure vwBiotaAssociateText, Line 7
Invalid object name 'tblBiotaAssociate'.
Msg 15151, Level 16, State 1, Line 1
Cannot find the object 'vwBiotaAssociateText', because it does not exist or you
do not have permission.
Msg 15151, Level 16, State 1, Line 2
Cannot find the object 'vwBiotaAssociateText', because it does not exist or you
do not have permission.
Adding Stored Procedures
[30%] Adding/Updating help_index...
All the Best,
- Aubrey
Original comment by aubreymoore2013@gmail.com
on 21 Oct 2012 at 2:09
Hi Aubrey,
Thanks for the update. As it turns out these error messages are expected, and
are an artifact of the script supporting really old BioLink database schemas.
Some time between version 1.0 and version 2.0 of BioLink the tblBiotaAssociate
table was deprecated in favour of the more generic tblAssociate table, thus
reflecting more accurately the possible modalities of associate relationships
(i.e. relationships can be formed between specimens, taxa and even just text,
and not just between two taxa). Newer versions of the BioLink schema,
therefore, don't have the tblBiotaAssociate table, nor the views/stored
procedures that utilize it.
When I get a chance I will update the documentation so that it explains what
these error messages mean. In the meantime, they can safely be ignored.
Regards, David.
Original comment by david.ba...@gmail.com
on 21 Oct 2012 at 4:26
Original issue reported on code.google.com by
mbp.revi...@gmail.com
on 28 Sep 2012 at 3:58Attachments: