On 21 Dec 2006, at 16:26, David Croft wrote:

Hi Arek,

you need to give us more details about the two main tables that you have there. There are some constraints under which Editor can work with two main tables.
Any chance of doing 'describe' on them and sending it to us

Well, if you like punishment, here are the 'describe's:


ok, here is the problem:

both tables belong to the same dataset:

test_reactome_18

which means that software will assume one is the subclass of the other
(which it isn't in this case because both have a single key and as you said they are unrelated) We need to add a some sort of informative exception to MEditor rather than driving
it into a 'frozen state' :)


if you want to fix it and they intend to be unrelated just change the dataset
name for one of them e.g.

call one

test_reactome_18

and the other

test_reactome_19

or something like that.

hopefully it should do the trick

a.


test_reactome_18__pathway__main:

| DB_ID | int(10) unsigned | YES | | NULL | | | _class | varchar(64) | YES | | NULL | | | _displayName | text | YES | | NULL | | | _doNotRelease | enum('TRUE','FALSE') | YES | | NULL | | | authored__displayName | text | YES | | NULL | | | authored_note | text | YES | | NULL | | | created__displayName | text | YES | | NULL | | | created_note | text | YES | | NULL | | | definition | text | YES | | NULL | | | evidenceType__displayName | text | YES | | NULL | | | evidenceType_definition | text | YES | | NULL | | | goBiologicalProcess__displayName | text | YES | | NULL | | | goBiologicalProcess_accession | text | YES | | NULL | | | goBiologicalProcess_definition | text | YES | | NULL | | | goBiologicalProcess_referenceDatabase__displayName | text | YES | | NULL | | | goBiologicalProcess_referenceDatabase_url | text | YES | | NULL | | | releaseDate | date | YES | | NULL | | | stableIdentifier_key | int(10) | YES | MUL | NULL | | | referencednasequence_concat | longtext | YES | | NULL | | | has_referencednasequence_info_bool | bigint(1) | YES | | NULL | | | referencemolecule_concat | longtext | YES | | NULL | | | has_referencemolecule_info_bool | bigint(1) | YES | | NULL | | | referencepeptidesequence_concat | longtext | YES | | NULL | | | has_referencepeptidesequence_info_bool | bigint(1) | YES | | NULL | |

test_reactome_18__reaction__main:

| DB_ID | int(10) unsigned | YES | | NULL | | | _class | varchar(64) | YES | | NULL | | | _displayName | text | YES | | NULL | | | _doNotRelease | enum('TRUE','FALSE') | YES | | NULL | | | authored__displayName | text | YES | | NULL | | | authored_note | text | YES | | NULL | | | created__displayName | text | YES | | NULL | | | created_note | text | YES | | NULL | | | definition | text | YES | | NULL | | | evidenceType__displayName | text | YES | | NULL | | | evidenceType_definition | text | YES | | NULL | | | goBiologicalProcess__displayName | text | YES | | NULL | | | goBiologicalProcess_accession | text | YES | | NULL | | | goBiologicalProcess_definition | text | YES | | NULL | | | goBiologicalProcess_referenceDatabase__displayName | text | YES | | NULL | | | goBiologicalProcess_referenceDatabase_url | text | YES | | NULL | | | inferredProt | text | YES | | NULL | | | maxHomologues | text | YES | | NULL | | | releaseDate | date | YES | | NULL | | | reverseReaction | int(10) unsigned | YES | | NULL | | | stableIdentifier_key | int(10) | YES | MUL | NULL | | | totalProt | text | YES | | NULL | | | referencednasequence_concat | longtext | YES | | NULL | | | has_referencednasequence_info_bool | bigint(1) | YES | | NULL | | | referencemolecule_concat | longtext | YES | | NULL | | | has_referencemolecule_info_bool | bigint(1) | YES | | NULL | | | referencepeptidesequence_concat | longtext | YES | | NULL | | | has_referencepeptidesequence_info_bool | bigint(1) | YES | | NULL | |

Cheers,

David.



------------------------------------------------------------------------ -------
Arek Kasprzyk
EMBL-European Bioinformatics Institute.
Wellcome Trust Genome Campus, Hinxton,
Cambridge CB10 1SD, UK.
Tel: +44-(0)1223-494606
Fax: +44-(0)1223-494468
------------------------------------------------------------------------ -------



Reply via email to