[BUG] Problem with many-to-one relationships inside DocumentDB

[meuriceloup]

Hi, This is the deployed TML schema:

entity Product {
    id : String
    orders -> Order[0..*]
}
entity Order {
    id : String
    products -> Product."Product.orders"[1]
}

documentdb DocumentDatabase {
    collections {
        Order : Order
        Product : Product
    }
}

Once deployed, I executed this insert statement: insert Product {id: "p2", orders: [Order {id: "o2"}, Order {id: "o3"}]}

the query finished with success but not sure it did what it was supposed to do... Indeed, I connected my MongoDB database to take a look at the physical structures and the inserted data. This is what I noticed:

1) the two orders were successfully inserted (see screenshot)

2) product 'p2' was also inserted BUT this product is linked to only one order , i.e., o3 (see screenshot)

The problem seems to be due to the fact that field 'Product.orders' is defined as String field and not as an array of strings...

[DavyLandman]

tnx for the bug report, I hope it's solved after we merge the new ql compiler.

[tvdstorm]

Hi @meuriceloup , same request as in for #67 , is this still an issue in the current version?