Project

General

Profile

Bug #33

can create same model twice with different types

Added by ronald - about 16 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Mulgara
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

The following is accepted by mulgara:
<br/>

<br/>
&nbsp;&nbsp;create &lt;<a href="local:///foo#m1&gt;;">local:///foo#m1&amp;gt;;</a>
<br/>
&nbsp;&nbsp;create &lt;<a href="local:///foo#m1">local:///foo#m1</a>&gt; &lt;<a href="http://mulgara.org/mulgara#XMLSchemaModel&gt;;">http://mulgara.org/mulgara#XMLSchemaModel&amp;gt;;</a>
<br/>

<br/>
This then results in a partially unusable database, as this
<br/>
error cannot be corrected anymore. E.g.
<br/>

<br/>
&nbsp;&nbsp;drop &lt;<a href="local:///foo#m1&gt;;">local:///foo#m1&amp;gt;;</a>
<br/>

<br/>
produces the error
<br/>

<br/>
&nbsp;&nbsp;Error resolving [$s $p $o $_from] from <a href="local:///foo#m1">local:///foo#m1</a>
<br/>
&nbsp;&nbsp;Model 287 has more than one type!
<br/>

<br/>
It would be more robust if the 'create' checked that the model type
<br/>
is the same in the case where the model already exists.
<br/>

#1

Updated by Andrae Muys - over 15 years ago

Fix merged into trunk as revision <a href="http://mulgara.org/trac/changeset/258">258</a>

Also available in: Atom PDF