Wow, you are on the bleeding edge. What is in master hasn't yet been released. It turns out that this not being possible is an oversight that will get fixed before releasing. We'll also scan for other areas that are like this.
> Wow, you are on the bleeding edge. What is in master hasn't yet been
> released. It turns out that this not being possible is an oversight that
> will get fixed before releasing. We'll also scan for other areas that are
> like this.
> Thanks for the report.
> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>> I think I have the latest version :
>> Revision: 038ec795c6dd69546d7f6a2f09dcf7**b909958330
>> Author: rstam
>> Date: 15.06.2012 23:16:41
>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote:
>> > What version of the driver are you using?
>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
We'd have to support that in the BsonSerializationInfoFinder... Which we can do, but then it would look kinda weird. Your [*] would be .First() or .Single()...
On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
> Or is there some general solution that turns arrays into scalars for > purposes of constructing these queries?
> I know this isn't legal C#, but this is the idea:
> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents any > element
> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>> Wow, you are on the bleeding edge. What is in master hasn't yet been >> released. It turns out that this not being possible is an oversight that >> will get fixed before releasing. We'll also scan for other areas that are >> like this.
>> Thanks for the report.
>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>> I think I have the latest version : >>> Revision: 038ec795c6dd69546d7f6a2f09dcf7**b909958330 >>> Author: rstam >>> Date: 15.06.2012 23:16:41
>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote: >>> > What version of the driver are you using?
>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
> We'd have to support that in the BsonSerializationInfoFinder... Which we
> can do, but then it would look kinda weird. Your [*] would be .First() or
> .Single()...
> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>> Or is there some general solution that turns arrays into scalars for
>> purposes of constructing these queries?
>> I know this isn't legal C#, but this is the idea:
>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents any
>> element
>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>> Wow, you are on the bleeding edge. What is in master hasn't yet been
>>> released. It turns out that this not being possible is an oversight that
>>> will get fixed before releasing. We'll also scan for other areas that are
>>> like this.
>>> Thanks for the report.
>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>> I think I have the latest version :
>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7****b909958330
>>>> Author: rstam
>>>> Date: 15.06.2012 23:16:41
>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote:
>>>> > What version of the driver are you using?
>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
On Tuesday, June 19, 2012 3:57:11 PM UTC-5, Robert Stam wrote:
> More like .OneOf()
> which we would have to define. First or Single don't sound right, they > already have defined meanings.
> On Tue, Jun 19, 2012 at 4:47 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>> We'd have to support that in the BsonSerializationInfoFinder... Which we >> can do, but then it would look kinda weird. Your [*] would be .First() or >> .Single()...
>> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>>> Or is there some general solution that turns arrays into scalars for >>> purposes of constructing these queries?
>>> I know this isn't legal C#, but this is the idea:
>>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents any >>> element
>>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>> Wow, you are on the bleeding edge. What is in master hasn't yet been >>>> released. It turns out that this not being possible is an oversight that >>>> will get fixed before releasing. We'll also scan for other areas that are >>>> like this.
>>>> Thanks for the report.
>>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>>> I think I have the latest version : >>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7****b909958330 >>>>> Author: rstam >>>>> Date: 15.06.2012 23:16:41
>>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote: >>>>> > What version of the driver are you using?
>>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
Man, MongoDB's handling of array fields in queries is really confusing me.
I always thought that when the target field was an array that the document
would match if any of the array elements matched. But apparently that's not
always true:
> On Tuesday, June 19, 2012 3:57:11 PM UTC-5, Robert Stam wrote:
>> More like .OneOf()
>> which we would have to define. First or Single don't sound right, they
>> already have defined meanings.
>> On Tue, Jun 19, 2012 at 4:47 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>> We'd have to support that in the BsonSerializationInfoFinder... Which
>>> we can do, but then it would look kinda weird. Your [*] would be .First()
>>> or .Single()...
>>> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>>>> Or is there some general solution that turns arrays into scalars for
>>>> purposes of constructing these queries?
>>>> I know this isn't legal C#, but this is the idea:
>>>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents any
>>>> element
>>>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>>> Wow, you are on the bleeding edge. What is in master hasn't yet been
>>>>> released. It turns out that this not being possible is an oversight that
>>>>> will get fixed before releasing. We'll also scan for other areas that are
>>>>> like this.
>>>>> Thanks for the report.
>>>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>>>> I think I have the latest version :
>>>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7******b909958330
>>>>>> Author: rstam
>>>>>> Date: 15.06.2012 23:16:41
>>>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote:
>>>>>> > What version of the driver are you using?
>>>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
Is there any new info on mongo as a service on the new azure? I saw some references to 10gen having a new service offering in the microsoft announcements a couple of weeks ago, but haven't found any new info on my searches?
I like the look of new azure, but want to avoid self hosting. I know app harbor all geared up with mongohq and the other competitor already integrated as services.
Please create a new thread when the question is on a different subject
What we announced as part of the "Meet Windows Azure" event was the MongoDB Installer for Windows Azure Virtual Machines ( http://www.mongodb.org/display/DOCS/MongoDB+Installer+for+Windows+Azure). We are working to make the process for installing/using/managing MongoDB on Windows Azure easier and more automated and the installer is the first in the tool chest.
On Wednesday, June 20, 2012 11:24:49 AM UTC-7, Daniel Harman wrote:
> Hi all,
> Is there any new info on mongo as a service on the new azure? I saw some > references to 10gen having a new service offering in the microsoft > announcements a couple of weeks ago, but haven't found any new info on my > searches?
> I like the look of new azure, but want to avoid self hosting. I know app > harbor all geared up with mongohq and the other competitor already > integrated as services.
How does threading work on this forum? I changed subject and removed any visible content from the previous message as was most convenient on an iPad. Very surprised it has threaded this together.
I'm still on iPad so no idea how to dethread given your reply also been threaded in.
Dan
Sent from my iPad
On 21 Jun 2012, at 00:53, sridhar <srid...@10gen.com> wrote:
> Please create a new thread when the question is on a different subject
> What we announced as part of the "Meet Windows Azure" event was the MongoDB Installer for Windows Azure Virtual Machines (http://www.mongodb.org/display/DOCS/MongoDB+Installer+for+Windows+Azure). We are working to make the process for installing/using/managing MongoDB on Windows Azure easier and more automated and the installer is the first in the tool chest.
> On Wednesday, June 20, 2012 11:24:49 AM UTC-7, Daniel Harman wrote:
> Hi all,
> Is there any new info on mongo as a service on the new azure? I saw some references to 10gen having a new service offering in the microsoft announcements a couple of weeks ago, but haven't found any new info on my searches?
> I like the look of new azure, but want to avoid self hosting. I know app harbor all geared up with mongohq and the other competitor already integrated as services.
On Thursday, June 21, 2012 8:27:13 AM UTC-5, Daniel Harman wrote:
> How does threading work on this forum? I changed subject and removed any > visible content from the previous message as was most convenient on an > iPad. Very surprised it has threaded this together.
> I'm still on iPad so no idea how to dethread given your reply also been > threaded in.
> Dan
> Sent from my iPad
> On 21 Jun 2012, at 00:53, sridhar <srid...@10gen.com> wrote:
> Please create a new thread when the question is on a different subject
> What we announced as part of the "Meet Windows Azure" event was the > MongoDB Installer for Windows Azure Virtual Machines ( > http://www.mongodb.org/display/DOCS/MongoDB+Installer+for+Windows+Azure). > We are working to make the process for installing/using/managing MongoDB > on Windows Azure easier and more automated and the installer is the first > in the tool chest.
> On Wednesday, June 20, 2012 11:24:49 AM UTC-7, Daniel Harman wrote:
>> Hi all,
>> Is there any new info on mongo as a service on the new azure? I saw some >> references to 10gen having a new service offering in the microsoft >> announcements a couple of weeks ago, but haven't found any new info on my >> searches?
>> I like the look of new azure, but want to avoid self hosting. I know app >> harbor all geared up with mongohq and the other competitor already >> integrated as services.
To start a new thread just send a brand new email to
mongodb-csharp@googlegroups.com instead of replying to an existing one. Or
create a new post using the Google Groups web interface.
Hitting reply and clearing the subject line and content area isn't enough.
There must be something preserved in the email headers that keeps it tied
to the original thread.
On Thu, Jun 21, 2012 at 9:27 AM, Daniel Harman <daniel.a.har...@gmail.com>wrote:
> How does threading work on this forum? I changed subject and removed any
> visible content from the previous message as was most convenient on an
> iPad. Very surprised it has threaded this together.
> I'm still on iPad so no idea how to dethread given your reply also been
> threaded in.
> Dan
> Sent from my iPad
> On 21 Jun 2012, at 00:53, sridhar <srid...@10gen.com> wrote:
> Please create a new thread when the question is on a different subject
> What we announced as part of the "Meet Windows Azure" event was the
> MongoDB Installer for Windows Azure Virtual Machines (
> http://www.mongodb.org/display/DOCS/MongoDB+Installer+for+Windows+Azure).
> We are working to make the process for installing/using/managing MongoDB
> on Windows Azure easier and more automated and the installer is the first
> in the tool chest.
> On Wednesday, June 20, 2012 11:24:49 AM UTC-7, Daniel Harman wrote:
>> Hi all,
>> Is there any new info on mongo as a service on the new azure? I saw some
>> references to 10gen having a new service offering in the microsoft
>> announcements a couple of weeks ago, but haven't found any new info on my
>> searches?
>> I like the look of new azure, but want to avoid self hosting. I know app
>> harbor all geared up with mongohq and the other competitor already
>> integrated as services.
@TM: We have pushed a new commit to master that should contain the code you need to do handle your situation. If you have some time, would you mind pulling the latest and verifying it fixes your issue. Thanks...
On Tuesday, June 19, 2012 4:19:09 PM UTC-5, Robert Stam wrote:
> Man, MongoDB's handling of array fields in queries is really confusing me. > I always thought that when the target field was an array that the document > would match if any of the array elements matched. But apparently that's not > always true:
> Looks like $ne at least is handled specially. I thought this would match > both documents, since both of them have some value that is $ne to "red".
> On Tue, Jun 19, 2012 at 5:03 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>> Agreed...
>> On Tuesday, June 19, 2012 3:57:11 PM UTC-5, Robert Stam wrote:
>>> More like .OneOf()
>>> which we would have to define. First or Single don't sound right, they >>> already have defined meanings.
>>> On Tue, Jun 19, 2012 at 4:47 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>> We'd have to support that in the BsonSerializationInfoFinder... Which >>>> we can do, but then it would look kinda weird. Your [*] would be .First() >>>> or .Single()...
>>>> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>>>>> Or is there some general solution that turns arrays into scalars for >>>>> purposes of constructing these queries?
>>>>> I know this isn't legal C#, but this is the idea:
>>>>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents any >>>>> element
>>>>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>>>> Wow, you are on the bleeding edge. What is in master hasn't yet been >>>>>> released. It turns out that this not being possible is an oversight that >>>>>> will get fixed before releasing. We'll also scan for other areas that are >>>>>> like this.
>>>>>> Thanks for the report.
>>>>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>>>>> I think I have the latest version : >>>>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7******b909958330 >>>>>>> Author: rstam >>>>>>> Date: 15.06.2012 23:16:41
>>>>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote: >>>>>>> > What version of the driver are you using?
>>>>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
> @TM: We have pushed a new commit to master that should contain the code > you need to do handle your situation. If you have some time, would you > mind pulling the latest and verifying it fixes your issue. Thanks...
> On Tuesday, June 19, 2012 4:19:09 PM UTC-5, Robert Stam wrote:
>> Man, MongoDB's handling of array fields in queries is really confusing >> me. I always thought that when the target field was an array that the >> document would match if any of the array elements matched. But apparently >> that's not always true:
>> Looks like $ne at least is handled specially. I thought this would match >> both documents, since both of them have some value that is $ne to "red".
>> On Tue, Jun 19, 2012 at 5:03 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>> Agreed...
>>> On Tuesday, June 19, 2012 3:57:11 PM UTC-5, Robert Stam wrote:
>>>> More like .OneOf()
>>>> which we would have to define. First or Single don't sound right, they >>>> already have defined meanings.
>>>> On Tue, Jun 19, 2012 at 4:47 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>>> We'd have to support that in the BsonSerializationInfoFinder... Which >>>>> we can do, but then it would look kinda weird. Your [*] would be .First() >>>>> or .Single()...
>>>>> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>>>>>> Or is there some general solution that turns arrays into scalars for >>>>>> purposes of constructing these queries?
>>>>>> I know this isn't legal C#, but this is the idea:
>>>>>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents >>>>>> any element
>>>>>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson <craiggwil...@gmail.com >>>>>> > wrote:
>>>>>>> Wow, you are on the bleeding edge. What is in master hasn't yet >>>>>>> been released. It turns out that this not being possible is an oversight >>>>>>> that will get fixed before releasing. We'll also scan for other areas that >>>>>>> are like this.
>>>>>>> Thanks for the report.
>>>>>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>>>>>> I think I have the latest version : >>>>>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7******b909958330 >>>>>>>> Author: rstam >>>>>>>> Date: 15.06.2012 23:16:41
>>>>>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote: >>>>>>>> > What version of the driver are you using?
>>>>>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
>>>>>>>> > > Hi,
>>>>>>>> > > I have a document like this in mongo:
Yes, you'll need an elemMatch for this. It would be awkward to do this in the a typed api as it would require getting a single element out of a list (Query<MyClass>.EQ(mc => mc.Access.Single().Id, 4712). Anyways, we don't currently support this via the typed api. If elemMatch isn't what you want here, you'll need to use the untyped query api.
> Am Donnerstag, 21. Juni 2012 15:34:02 UTC+2 schrieb craiggwilson:
>> @TM: We have pushed a new commit to master that should contain the code >> you need to do handle your situation. If you have some time, would you >> mind pulling the latest and verifying it fixes your issue. Thanks...
>> On Tuesday, June 19, 2012 4:19:09 PM UTC-5, Robert Stam wrote:
>>> Man, MongoDB's handling of array fields in queries is really confusing >>> me. I always thought that when the target field was an array that the >>> document would match if any of the array elements matched. But apparently >>> that's not always true:
>>> Looks like $ne at least is handled specially. I thought this would match >>> both documents, since both of them have some value that is $ne to "red".
>>> On Tue, Jun 19, 2012 at 5:03 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>> Agreed...
>>>> On Tuesday, June 19, 2012 3:57:11 PM UTC-5, Robert Stam wrote:
>>>>> More like .OneOf()
>>>>> which we would have to define. First or Single don't sound right, they >>>>> already have defined meanings.
>>>>> On Tue, Jun 19, 2012 at 4:47 PM, craiggwilson <craiggwil...@gmail.com>wrote:
>>>>>> We'd have to support that in the BsonSerializationInfoFinder... >>>>>> Which we can do, but then it would look kinda weird. Your [*] would be >>>>>> .First() or .Single()...
>>>>>> On Tuesday, June 19, 2012 3:37:29 PM UTC-5, Robert Stam wrote:
>>>>>>> Or is there some general solution that turns arrays into scalars for >>>>>>> purposes of constructing these queries?
>>>>>>> I know this isn't legal C#, but this is the idea:
>>>>>>> Query<User>.EQ(x => x.AccomodationIds[*], 1) // where * represents >>>>>>> any element
>>>>>>> On Tue, Jun 19, 2012 at 4:34 PM, craiggwilson < >>>>>>> craiggwil...@gmail.com> wrote:
>>>>>>>> Wow, you are on the bleeding edge. What is in master hasn't yet >>>>>>>> been released. It turns out that this not being possible is an oversight >>>>>>>> that will get fixed before releasing. We'll also scan for other areas that >>>>>>>> are like this.
>>>>>>>> Thanks for the report.
>>>>>>>> On Tuesday, June 19, 2012 10:16:03 AM UTC-5, TM wrote:
>>>>>>>>> I think I have the latest version : >>>>>>>>> Revision: 038ec795c6dd69546d7f6a2f09dcf7******b909958330 >>>>>>>>> Author: rstam >>>>>>>>> Date: 15.06.2012 23:16:41
>>>>>>>>> On 19 Jun., 16:06, craiggwilson <craiggwil...@gmail.com> wrote: >>>>>>>>> > What version of the driver are you using?
>>>>>>>>> > On Tuesday, June 19, 2012 3:53:38 AM UTC-5, TM wrote:
>>>>>>>>> > > Hi,
>>>>>>>>> > > I have a document like this in mongo: