Why are we using registry for this at the first place ?
On Sat, May 10, 2014 at 6:54 AM, Nuwan Dias <[email protected]> wrote: > On Fri, May 9, 2014 at 9:25 PM, Ajith Vitharana <[email protected]> wrote: > >> Hi Uvindra, >> >> >> On Fri, May 9, 2014 at 5:47 PM, Uvindra Dias Jayasinha >> <[email protected]>wrote: >> >>> This limitation was highlighted during the discussion we had with Ajith >>> just before work on the API Store forum was started. As I mentioned we ran >>> into the same limitation when developing the development governance >>> solution. The text area that was to store custom javascript rules could not >>> accommodate anything exceeding 1000 characters. In the end after discussing >>> with Senaka we solved the problem by increasing the column size of >>> REG_VALUE to 5000 and changing the DB scripts that were shipped with the >>> solution accordingly. >>> >> >> So, what happen when the length is 5001 ? :) >> > > Yes, I think we should someday fix this rxt field to property mapping. > Otherwise there's no point in having a field called 'text-area' in the rxt > right? Its capabilities become limited to same as the 'text' field. > Besides, from a user POV, there's no point in creating a property in the > rxt for each field. And when you comes across the need to store more than > 1000 characters in an artifact, you're totally blocked from doing so and > have to resort to other complicated measures. > > So I suggest that we make it a point to fix this urgently when > appropriate. Kernel 4.3.0 or C5 at least. Sooner the better :) > >> >> Thanks. >> Ajith. >> >>> >>> >>> On Fri, May 9, 2014 at 5:29 PM, Nuwan Dias <[email protected]> wrote: >>> >>>> Hi Ajith, >>>> >>>> We're developing a forum for the API Store using the registry as the >>>> storage medium. Each topic/reply is stored in the registry as an artifact. >>>> Topics/Replies have a rich text editor which supports code blocks, etc. >>>> This text-area has been mapped to a text-area field in the rxt. So limiting >>>> the characters to < 1000 is not very feasible in this scenario. >>>> >>>> Are you saying that increasing the column size of REG_VALUE is not a >>>> good idea? >>>> >>>> Thanks, >>>> NuwanD. >>>> >>>> >>>> On Fri, May 9, 2014 at 5:22 PM, Ajith Vitharana <[email protected]>wrote: >>>> >>>>> Hi Nuwan, >>>>> >>>>> We store the each filed as properties of the artifacts, that is the >>>>> data model used. Anyway, having the 1000 characters for the given field is >>>>> a special case. >>>>> So, it is not better to increase the default schema to handle this use >>>>> case. >>>>> >>>>> Can't we limit the characters length for that text-area ? >>>>> >>>>> Thanks. >>>>> Ajith. >>>>> >>>>> >>>>> On Fri, May 9, 2014 at 3:18 PM, Nuwan Dias <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have an rxt on which I am using a text-area field. However I get >>>>>> the following error if I am to put more that 1000 characters in the >>>>>> field. >>>>>> >>>>>> org.h2.jdbc.JdbcSQLException: Value too long for column "REG_VALUE >>>>>> VARCHAR(1000)": "STRINGDECODE('<table><tbody><tr><td >>>>>> class=\""votecell\""><div class=\""vote\"">\n <span >>>>>> class=\""vote-count-post \"">2</span>\n ... (1107)"; SQL statement: >>>>>> INSERT INTO REG_PROPERTY (REG_NAME, REG_VALUE, REG_TENANT_ID) VALUES >>>>>> (?, ?, ?) [90005-140] >>>>>> >>>>>> The reason for the above problem is due to the fact that each field >>>>>> in the rxt is also saved as a rxt property. The column length in the >>>>>> database for the property value is 1000 characters. Therefore basically >>>>>> its >>>>>> not possible to have a field in the rxt which is more than 1000 >>>>>> characters >>>>>> long. >>>>>> >>>>>> I see this as a serious limitation. The only possible workaround I >>>>>> see is to increase the column size. Any other solutions to this? Why do >>>>>> we >>>>>> need to have a property corresponding to each field in the rxt? If we can >>>>>> get rid of that, then we're good IMO. >>>>>> >>>>>> Thanks, >>>>>> NuwanD. >>>>>> >>>>>> -- >>>>>> Nuwan Dias >>>>>> >>>>>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>>>>> email : [email protected] >>>>>> Phone : +94 777 775 729 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ajith Vitharana. >>>>> WSO2 Inc. - http://wso2.org >>>>> Email : [email protected] >>>>> Mobile : +94772217350 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>>> email : [email protected] >>>> Phone : +94 777 775 729 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Regards, >>> Uvindra >>> >>> Mobile: 777733962 >>> >> >> >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : [email protected] >> Mobile : +94772217350 >> >> > > > -- > Nuwan Dias > > Associate Tech Lead - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Suresh Attanayake Senior Software Engineer; WSO2 Inc. http://wso2.com/ Blog : http://sureshatt.blogspot.com/ Web : http://www.ssoarcade.com/ Facebook : https://www.facebook.com/IdentityWorld Twitter : https://twitter.com/sureshatt LinkedIn : http://lk.linkedin.com/in/sureshatt Mobile : +94755012060 Mobile : +016166171172
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
