On Thu, Jun 9, 2016 at 7:29 AM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:
>
>
> On Thu, Jun 9, 2016 at 2:03 AM, Sriskandarajah Suhothayan
> wrote:
>
>> I think the way to handle this is by sending some default value, or
>> identify nulls and replacing them with
On Thu, Jun 9, 2016 at 2:03 AM, Sriskandarajah Suhothayan
wrote:
> I think the way to handle this is by sending some default value, or
> identify nulls and replacing them with default value.
> I think the trick here is to find a default value that users cannot
> create. How about
I think the way to handle this is by sending some default value, or
identify nulls and replacing them with default value.
I think the trick here is to find a default value that users cannot create.
How about using "NOT AVAILABLE" with space. I think IS does not allow
users to create username with
On Tue, Jun 7, 2016 at 6:35 PM, Hasintha Indrajee wrote:
> Hi Damith,
>
> For the time being we can follow this approach. But this seems like a
> standard problem we may face in other products as well. Any standard way of
> handling this ? Any ideas for handling this issue in
Hi Damith,
For the time being we can follow this approach. But this seems like a
standard problem we may face in other products as well. Any standard way of
handling this ? Any ideas for handling this issue in future ?
On Tue, Jun 7, 2016 at 12:32 PM, Damith Wickramasinghe
Hi Johann and all,
Our decided approach was to send a empty string for all the cases from IS
side and from DAS after retrieving data, provide a default string with some
style to show that its a special empty case. But in lucene we cannot have
empty attributes since they cannot be indexed and
Hi,
When it comes to authentication scenarios in some cases we cannot specify
roles etc to publishing events eg:- non existing user tried to login with
username and password. Then for the said events roles attribute will be
empty/null .
Also as discussed with Pulasthi there can be other