LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Date in Field 1 = Date in Field 2

    Employee
    Posted 03-24-2010 20:35

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Rapkat

    I have 2 Fields they are both bdate type

    Field 1 is a date that is either today or in the future
    Field 2 is a specific date

    I want to know all the Field 1's that are equal to Field 2, what operators do I use to work with bdate type fields.


  • 2.  RE: Date in Field 1 = Date in Field 2

    Employee
    Posted 03-25-2010 08:39

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    If they are both date fields, you should be able to use just an ==
    See attached for an example.

    Cheers
    Rich
    Attachments:
    dateCompare.brg


  • 3.  RE: Date in Field 1 = Date in Field 2

    Employee
    Posted 03-25-2010 14:57

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: Rapkat

    I did try that but it returned all the records, so I try some other things and I changed it around to this instead of comparing 2 fields, and it works:

    emit * where
    'Review_Date' == date().str().toDate("CCYY-MM-DD")


  • 4.  RE: Date in Field 1 = Date in Field 2

    Employee
    Posted 03-26-2010 08:16

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rboccuzzi

    Is it possible when you first tried the date field direct comparison that you used a single = instead of a ==? That would cause all fields to be matched.

    If you are able to reproduce this with a == in the comparison, I would be interested in looking at the node and data, if possible. Could you use the procedure described
    here to attach your node and data with the issue?

    Cheers
    Rich