Hi Ruwan, On Fri, Oct 2, 2015 at 1:09 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
> Hi Ishara, > >>In Identity server we started to persist session date with its updated > timestamp. And retrieve the latest data object related to > given session. > >>If it's only supported for seconds we get duplicate entries. In that > case we have to go for fractional seconds in timestamp > or will have to store it in another data type. > > I think tying up with timestamp for any uniqueness is going to be > problematic even if we select the most granular time resolution provided by > the hardware. > Thats true and its depend on the use case too. In our use case we don't depend only on the timestamp and we can't expect nano second level time different between session participants. In that case I believe we can go ahead with our approach. Thanks, Ishara > For example lets say an IoT device sends more than one request in fraction > of nano second and this might be causing problems down the pipeline/in the > future. > So I would suggest a changing the dependency of using timestamp for any > uniqueness/ latest check by adding/appending a sequence number, if it is > the case. > > Cheers, > Ruwan > > > On Fri, Oct 2, 2015 at 10:05 AM, Ishara Karunarathna <isha...@wso2.com> > wrote: > >> Hi Shankar, >> >> On Thu, Oct 1, 2015 at 9:54 PM, Selvaratnam Uthaiyashankar < >> shan...@wso2.com> wrote: >> >>> Is this support (fraction of second) there in other RDBMS (Oracle, >>> MSSQL, etc?). If it is only Mysql 5.6.4 +, then we shouldn't use IMO. If >>> this support is there in all other RDBMS, then it should be ok. >>> >>> I checked with Oracle, MSSQL, PostgreSQL, Informix and DB2. All support >> for fraction of seconds. >> >> Thanks, >> Ishara >> [1] >> http://docs.oracle.com/cd/B19306_01/server.102/b14200/sql_elements001.htm#i54330 >> [2] https://msdn.microsoft.com/en-us/library/ms187819.aspx >> [3] http://www.postgresql.org/docs/9.1/static/datatype-datetime.html >> [4] >> https://www-01.ibm.com/support/knowledgecenter/SSGU8G_12.1.0/com.ibm.sqlr.doc/ids_sqr_110.htm >> [5] >> https://www-304.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/com.ibm.db2z10.doc.intro/src/tpc/db2z_datetimetimestamp.dita >> >>> On Thu, Oct 1, 2015 at 9:40 PM, Ishara Karunarathna <isha...@wso2.com> >>> wrote: >>> >>>> Hi Shankar, >>>> >>>> On Thu, Oct 1, 2015 at 7:45 PM, Selvaratnam Uthaiyashankar < >>>> shan...@wso2.com> wrote: >>>> >>>>> Normally, we should keep the compatibility with older versions. >>>>> >>>>> Is there any specific reason why you need upto microsecond precision >>>>> for the timestamp? >>>>> >>>> by default mysql support for seconds. >>>> In Identity server we started to persist session date with its updated >>>> timestamp. And retrieve the latest data object related to >>>> given session. >>>> If it's only supported for seconds we get duplicate entries. In that >>>> case we have to go for fractional seconds in timestamp >>>> or will have to store it in another data type. >>>> >>>> Thanks, >>>> Ishara >>>> >>>>> >>>>> On Wed, Sep 30, 2015 at 10:35 PM, Ishara Karunarathna < >>>>> isha...@wso2.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> For example In mysql version 5.6.4 (released on February 5, 2013 ) >>>>>> onwards [1] it support for >>>>>> fractional seconds for TIMESTAMP values, with up to microseconds (6 >>>>>> digits) >>>>>> >>>>>> But if we write scripts to get that features it won't work with older >>>>>> versions. >>>>>> So can we write scripts to work only with mysql version 5.6.4 and >>>>>> latest or should we support for old versions ?. >>>>>> >>>>>> Thanks, >>>>>> Ishara >>>>>> >>>>>> [1] >>>>>> http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html#mysql-nutshell-additions >>>>>> -- >>>>>> Ishara Karunarathna >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>>> >>>>>> email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: >>>>>> +94717996791 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> S.Uthaiyashankar >>>>> VP Engineering >>>>> WSO2 Inc. >>>>> http://wso2.com/ - "lean . enterprise . middleware" >>>>> >>>>> Phone: +94 714897591 >>>>> >>>> >>>> >>>> >>>> -- >>>> Ishara Karunarathna >>>> Senior Software Engineer >>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>> >>>> email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: >>>> +94717996791 >>>> >>> >>> >>> >>> -- >>> S.Uthaiyashankar >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com/ - "lean . enterprise . middleware" >>> >>> Phone: +94 714897591 >>> >> >> >> >> -- >> Ishara Karunarathna >> Senior Software Engineer >> WSO2 Inc. - lean . enterprise . middleware | wso2.com >> >> email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: >> +94717996791 >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Ruwan Abeykoon* > *Architect,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: ruw...@wso2.com > -- Ishara Karunarathna Senior Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile: +94717996791
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
