Mixing
Inserting an array into a child collection in MongoDB is omitting the _t Discriminator
Given these classes:
public class Parent
{
public IEnumerable<IChild> Children { get; set; }
}
public interface IChild { }
public class Child : IChild { }
Inserting the Children property as an array like this:
using MongoDB.Driver;
using System.Collections.Generic;
namespace TestConsoleApp
{
class Program
{
static void Main(string args)
{
var db = new MongoClient().GetDatabase("Test");
var collection = db.GetCollection<Parent>("Parent");
collection.InsertOne(new Parent { Children = new { new Child() } });
}
}
}
The _t Discriminator is missing in the DB:
{
"_id":"5bf6aef6c0beccc414b70d45",
"Child":[{}]
}
If I use a List instead:
collection.InsertOne(new Parent { Children = new List<IChild> { new Child() } });
The _t Discriminator is set correctly:
{
"_id":"5bf6b074c0beccc414b70dc2",
"Children":[{"_t":"Child"}]
}
This seems like a bug or at the very least a very unintuitive behavior.
Additional information:
The behavior is a problem because the missing _t Discriminator is causing an Exception when deserializing the object:
System.FormatException: 'An error occurred while deserializing the Children property of class TestConsoleApp.Parent: Unable to determine actual type of object to deserialize for interface type TestConsoleApp.IChild.'
c# .net mongodb mongodb-.net-driver
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
add a comment |
Given these classes:
public class Parent
{
public IEnumerable<IChild> Children { get; set; }
}
public interface IChild { }
public class Child : IChild { }
Inserting the Children property as an array like this:
using MongoDB.Driver;
using System.Collections.Generic;
namespace TestConsoleApp
{
class Program
{
static void Main(string args)
{
var db = new MongoClient().GetDatabase("Test");
var collection = db.GetCollection<Parent>("Parent");
collection.InsertOne(new Parent { Children = new { new Child() } });
}
}
}
The _t Discriminator is missing in the DB:
{
"_id":"5bf6aef6c0beccc414b70d45",
"Child":[{}]
}
If I use a List instead:
collection.InsertOne(new Parent { Children = new List<IChild> { new Child() } });
The _t Discriminator is set correctly:
{
"_id":"5bf6b074c0beccc414b70dc2",
"Children":[{"_t":"Child"}]
}
This seems like a bug or at the very least a very unintuitive behavior.
Additional information:
The behavior is a problem because the missing _t Discriminator is causing an Exception when deserializing the object:
System.FormatException: 'An error occurred while deserializing the Children property of class TestConsoleApp.Parent: Unable to determine actual type of object to deserialize for interface type TestConsoleApp.IChild.'
c# .net mongodb mongodb-.net-driver
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
if it works for the list, then why use an array? You can always callToList()extension on array to get working list
– Nkosi
Nov 27 '18 at 12:05
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
At the first look the type of the array element (Child) is different from the type of the list element (List<IChild>). I would assume that if you usenew IChild { new Child() },the array code will work. And if you usenew List<Child> { new Child() }, the list code will stop working.
– Ivan Stoev
Nov 27 '18 at 14:27
new IChild { new Child() }does not work
– Tim Pohlmann
Nov 27 '18 at 15:03
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18
add a comment |
Given these classes:
public class Parent
{
public IEnumerable<IChild> Children { get; set; }
}
public interface IChild { }
public class Child : IChild { }
Inserting the Children property as an array like this:
using MongoDB.Driver;
using System.Collections.Generic;
namespace TestConsoleApp
{
class Program
{
static void Main(string args)
{
var db = new MongoClient().GetDatabase("Test");
var collection = db.GetCollection<Parent>("Parent");
collection.InsertOne(new Parent { Children = new { new Child() } });
}
}
}
The _t Discriminator is missing in the DB:
{
"_id":"5bf6aef6c0beccc414b70d45",
"Child":[{}]
}
If I use a List instead:
collection.InsertOne(new Parent { Children = new List<IChild> { new Child() } });
The _t Discriminator is set correctly:
{
"_id":"5bf6b074c0beccc414b70dc2",
"Children":[{"_t":"Child"}]
}
This seems like a bug or at the very least a very unintuitive behavior.
Additional information:
The behavior is a problem because the missing _t Discriminator is causing an Exception when deserializing the object:
System.FormatException: 'An error occurred while deserializing the Children property of class TestConsoleApp.Parent: Unable to determine actual type of object to deserialize for interface type TestConsoleApp.IChild.'
c# .net mongodb mongodb-.net-driver
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
Given these classes:
public class Parent
{
public IEnumerable<IChild> Children { get; set; }
}
public interface IChild { }
public class Child : IChild { }
Inserting the Children property as an array like this:
using MongoDB.Driver;
using System.Collections.Generic;
namespace TestConsoleApp
{
class Program
{
static void Main(string args)
{
var db = new MongoClient().GetDatabase("Test");
var collection = db.GetCollection<Parent>("Parent");
collection.InsertOne(new Parent { Children = new { new Child() } });
}
}
}
The _t Discriminator is missing in the DB:
{
"_id":"5bf6aef6c0beccc414b70d45",
"Child":[{}]
}
If I use a List instead:
collection.InsertOne(new Parent { Children = new List<IChild> { new Child() } });
The _t Discriminator is set correctly:
{
"_id":"5bf6b074c0beccc414b70dc2",
"Children":[{"_t":"Child"}]
}
This seems like a bug or at the very least a very unintuitive behavior.
Additional information:
The behavior is a problem because the missing _t Discriminator is causing an Exception when deserializing the object:
System.FormatException: 'An error occurred while deserializing the Children property of class TestConsoleApp.Parent: Unable to determine actual type of object to deserialize for interface type TestConsoleApp.IChild.'
c# .net mongodb mongodb-.net-driver
c# .net mongodb mongodb-.net-driver
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
asked Nov 22 '18 at 13:45
Tim PohlmannTim Pohlmann
1,8701542
1,8701542
if it works for the list, then why use an array? You can always callToList()extension on array to get working list
– Nkosi
Nov 27 '18 at 12:05
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
At the first look the type of the array element (Child) is different from the type of the list element (List<IChild>). I would assume that if you usenew IChild { new Child() },the array code will work. And if you usenew List<Child> { new Child() }, the list code will stop working.
– Ivan Stoev
Nov 27 '18 at 14:27
new IChild { new Child() }does not work
– Tim Pohlmann
Nov 27 '18 at 15:03
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18
add a comment |
if it works for the list, then why use an array? You can always callToList()extension on array to get working list
– Nkosi
Nov 27 '18 at 12:05
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
At the first look the type of the array element (Child) is different from the type of the list element (List<IChild>). I would assume that if you usenew IChild { new Child() },the array code will work. And if you usenew List<Child> { new Child() }, the list code will stop working.
– Ivan Stoev
Nov 27 '18 at 14:27
new IChild { new Child() }does not work
– Tim Pohlmann
Nov 27 '18 at 15:03
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18
if it works for the list, then why use an array? You can always call
ToList() extension on array to get working list– Nkosi
Nov 27 '18 at 12:05
if it works for the list, then why use an array? You can always call
ToList() extension on array to get working list– Nkosi
Nov 27 '18 at 12:05
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
At the first look the type of the array element (
Child) is different from the type of the list element (List<IChild>). I would assume that if you use new IChild { new Child() }, the array code will work. And if you use new List<Child> { new Child() } , the list code will stop working.– Ivan Stoev
Nov 27 '18 at 14:27
At the first look the type of the array element (
Child) is different from the type of the list element (List<IChild>). I would assume that if you use new IChild { new Child() }, the array code will work. And if you use new List<Child> { new Child() } , the list code will stop working.– Ivan Stoev
Nov 27 '18 at 14:27
new IChild { new Child() } does not work– Tim Pohlmann
Nov 27 '18 at 15:03
new IChild { new Child() } does not work– Tim Pohlmann
Nov 27 '18 at 15:03
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18
add a comment |
2 Answers
2
active
oldest
votes
The issue is caused because there is no implementation class of IChild interface discovered by mongo. In other words mongo driver does not know that IChild implementation must be created using Child class. Thats why it is adding _t Discriminator.
To solve the issue you can specify implied serialization.
public class Parent
{
[BsonSerializer(typeof(ImpliedImplementationInterfaceSerializer<IEnumerable<IChild>, IEnumerable<Child>>))]
public IEnumerable<IChild> Children { get; set; }
}
With this attribute it will not create _t Discrimination but will use Child class for deserializing.
In case if you want to force discriminator on dynamic instances you can use
[BsonDiscriminator(Required = true)]
public class Child : IChild { }
Note that this header should be added to all classes for which you need to force discriminator creation.
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
add a comment |
In my opinion, it's a bug as you said, actually considering the exception you mentioned its probably a bug.
Anyway, this is the GitHub repository of the project https://github.com/mongodb/mongo-csharp-driver.
In the README.md you can find instructions about how you report a bug (Please tell me if you are not going to report it so I'll do so).
In the meantime, I think the best solution will be replacing the IEnumerable<IChild> with IList<IChild> to prevent other programmers from inserting data the wrong way.
Edit: Please check if IList Solves the problem because this line is compiling (at least for me)
public static IList<int> Ints { get; set; }
static void Main(string args)
{
Ints = new {1,2,3,4};
Console.WriteLine("Hello World!");
}
If it does not solve your problem I would have just used List<IChild>. It's not pretty but it will work.
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
IListis not helping since, as you've mentioned, an array is also anIList. I'm gonna useListas a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.
– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432370%2finserting-an-array-into-a-child-collection-in-mongodb-is-omitting-the-t-discrim%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue is caused because there is no implementation class of IChild interface discovered by mongo. In other words mongo driver does not know that IChild implementation must be created using Child class. Thats why it is adding _t Discriminator.
To solve the issue you can specify implied serialization.
public class Parent
{
[BsonSerializer(typeof(ImpliedImplementationInterfaceSerializer<IEnumerable<IChild>, IEnumerable<Child>>))]
public IEnumerable<IChild> Children { get; set; }
}
With this attribute it will not create _t Discrimination but will use Child class for deserializing.
In case if you want to force discriminator on dynamic instances you can use
[BsonDiscriminator(Required = true)]
public class Child : IChild { }
Note that this header should be added to all classes for which you need to force discriminator creation.
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
add a comment |
The issue is caused because there is no implementation class of IChild interface discovered by mongo. In other words mongo driver does not know that IChild implementation must be created using Child class. Thats why it is adding _t Discriminator.
To solve the issue you can specify implied serialization.
public class Parent
{
[BsonSerializer(typeof(ImpliedImplementationInterfaceSerializer<IEnumerable<IChild>, IEnumerable<Child>>))]
public IEnumerable<IChild> Children { get; set; }
}
With this attribute it will not create _t Discrimination but will use Child class for deserializing.
In case if you want to force discriminator on dynamic instances you can use
[BsonDiscriminator(Required = true)]
public class Child : IChild { }
Note that this header should be added to all classes for which you need to force discriminator creation.
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
add a comment |
The issue is caused because there is no implementation class of IChild interface discovered by mongo. In other words mongo driver does not know that IChild implementation must be created using Child class. Thats why it is adding _t Discriminator.
To solve the issue you can specify implied serialization.
public class Parent
{
[BsonSerializer(typeof(ImpliedImplementationInterfaceSerializer<IEnumerable<IChild>, IEnumerable<Child>>))]
public IEnumerable<IChild> Children { get; set; }
}
With this attribute it will not create _t Discrimination but will use Child class for deserializing.
In case if you want to force discriminator on dynamic instances you can use
[BsonDiscriminator(Required = true)]
public class Child : IChild { }
Note that this header should be added to all classes for which you need to force discriminator creation.
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
The issue is caused because there is no implementation class of IChild interface discovered by mongo. In other words mongo driver does not know that IChild implementation must be created using Child class. Thats why it is adding _t Discriminator.
To solve the issue you can specify implied serialization.
public class Parent
{
[BsonSerializer(typeof(ImpliedImplementationInterfaceSerializer<IEnumerable<IChild>, IEnumerable<Child>>))]
public IEnumerable<IChild> Children { get; set; }
}
With this attribute it will not create _t Discrimination but will use Child class for deserializing.
In case if you want to force discriminator on dynamic instances you can use
[BsonDiscriminator(Required = true)]
public class Child : IChild { }
Note that this header should be added to all classes for which you need to force discriminator creation.
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
edited Dec 4 '18 at 22:52
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
answered Dec 3 '18 at 22:28
Vadim AlekseevskyVadim Alekseevsky
38219
38219
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
add a comment |
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
I want the _t Discriminator to be created though, because I have multiple implementations of IChild.
– Tim Pohlmann
Dec 4 '18 at 8:51
1
1
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
If you want to force discriminator creation on dynamic instances you can add the header to your class instance [BsonDiscriminator(Required = true)] public class Child : IChild { } Just edited answer
– Vadim Alekseevsky
Dec 4 '18 at 22:51
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
That actually worked. Pretty inconvenient but it's a decent workaround. Thanks.
– Tim Pohlmann
Dec 5 '18 at 8:45
add a comment |
In my opinion, it's a bug as you said, actually considering the exception you mentioned its probably a bug.
Anyway, this is the GitHub repository of the project https://github.com/mongodb/mongo-csharp-driver.
In the README.md you can find instructions about how you report a bug (Please tell me if you are not going to report it so I'll do so).
In the meantime, I think the best solution will be replacing the IEnumerable<IChild> with IList<IChild> to prevent other programmers from inserting data the wrong way.
Edit: Please check if IList Solves the problem because this line is compiling (at least for me)
public static IList<int> Ints { get; set; }
static void Main(string args)
{
Ints = new {1,2,3,4};
Console.WriteLine("Hello World!");
}
If it does not solve your problem I would have just used List<IChild>. It's not pretty but it will work.
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
IListis not helping since, as you've mentioned, an array is also anIList. I'm gonna useListas a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.
– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
add a comment |
In my opinion, it's a bug as you said, actually considering the exception you mentioned its probably a bug.
Anyway, this is the GitHub repository of the project https://github.com/mongodb/mongo-csharp-driver.
In the README.md you can find instructions about how you report a bug (Please tell me if you are not going to report it so I'll do so).
In the meantime, I think the best solution will be replacing the IEnumerable<IChild> with IList<IChild> to prevent other programmers from inserting data the wrong way.
Edit: Please check if IList Solves the problem because this line is compiling (at least for me)
public static IList<int> Ints { get; set; }
static void Main(string args)
{
Ints = new {1,2,3,4};
Console.WriteLine("Hello World!");
}
If it does not solve your problem I would have just used List<IChild>. It's not pretty but it will work.
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
IListis not helping since, as you've mentioned, an array is also anIList. I'm gonna useListas a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.
– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
add a comment |
In my opinion, it's a bug as you said, actually considering the exception you mentioned its probably a bug.
Anyway, this is the GitHub repository of the project https://github.com/mongodb/mongo-csharp-driver.
In the README.md you can find instructions about how you report a bug (Please tell me if you are not going to report it so I'll do so).
In the meantime, I think the best solution will be replacing the IEnumerable<IChild> with IList<IChild> to prevent other programmers from inserting data the wrong way.
Edit: Please check if IList Solves the problem because this line is compiling (at least for me)
public static IList<int> Ints { get; set; }
static void Main(string args)
{
Ints = new {1,2,3,4};
Console.WriteLine("Hello World!");
}
If it does not solve your problem I would have just used List<IChild>. It's not pretty but it will work.
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
In my opinion, it's a bug as you said, actually considering the exception you mentioned its probably a bug.
Anyway, this is the GitHub repository of the project https://github.com/mongodb/mongo-csharp-driver.
In the README.md you can find instructions about how you report a bug (Please tell me if you are not going to report it so I'll do so).
In the meantime, I think the best solution will be replacing the IEnumerable<IChild> with IList<IChild> to prevent other programmers from inserting data the wrong way.
Edit: Please check if IList Solves the problem because this line is compiling (at least for me)
public static IList<int> Ints { get; set; }
static void Main(string args)
{
Ints = new {1,2,3,4};
Console.WriteLine("Hello World!");
}
If it does not solve your problem I would have just used List<IChild>. It's not pretty but it will work.
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
edited Nov 29 '18 at 18:02
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
answered Nov 29 '18 at 17:45
yonBavyonBav
3381311
3381311
IListis not helping since, as you've mentioned, an array is also anIList. I'm gonna useListas a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.
– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
add a comment |
IListis not helping since, as you've mentioned, an array is also anIList. I'm gonna useListas a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.
– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
IList is not helping since, as you've mentioned, an array is also an IList. I'm gonna use List as a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.– Tim Pohlmann
Nov 30 '18 at 7:49
IList is not helping since, as you've mentioned, an array is also an IList. I'm gonna use List as a workaround. I'm not gonna report the bug because I don't want to create an account with their Jira system right now. Feel free to do so, though.– Tim Pohlmann
Nov 30 '18 at 7:49
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
No problem i will :)
– yonBav
Nov 30 '18 at 8:38
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
Did you post the bugreport? If so, could you link it?
– Tim Pohlmann
Dec 6 '18 at 8:37
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
jira.mongodb.org/browse/CSHARP-2458
– yonBav
Dec 18 '18 at 6:53
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
To be honest i forgot but i did it now. The link is above.
– yonBav
Dec 18 '18 at 6:55
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432370%2finserting-an-array-into-a-child-collection-in-mongodb-is-omitting-the-t-discrim%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
if it works for the list, then why use an array? You can always call
ToList()extension on array to get working list– Nkosi
Nov 27 '18 at 12:05
sure, but that's easy to forget. I would like to prevent programming errors like that. I could just change the property type from IEnumerable to List but I would like to avoid that.
– Tim Pohlmann
Nov 27 '18 at 13:49
At the first look the type of the array element (
Child) is different from the type of the list element (List<IChild>). I would assume that if you usenew IChild { new Child() },the array code will work. And if you usenew List<Child> { new Child() }, the list code will stop working.– Ivan Stoev
Nov 27 '18 at 14:27
new IChild { new Child() }does not work– Tim Pohlmann
Nov 27 '18 at 15:03
When it comes to collections in DTOs, I always avoid using interfaces and use concrete implementations. It seems that it avoids a host of problems, for whatever the reason. I think it is due to the fact that interfaces are too abstract to expect consistent development philosophies and treatment across different tools.
– theMayer
Nov 29 '18 at 18:18