Thanks for the info! I solved my issue in another way. Regards, Roald
On Sun, Mar 8, 2015 at 10:31 PM, Paul Robert Marino <prmari...@gmail.com> wrote: > Roald > Last I had checked in MySQL VARCHAR(255) was the max size. Now it seems > they made a change to VARCHAR to allow for sizes over 255 the new max is > 65,535 bytes -2 which equals 65,533 characters. > So yes that should work just fine. Just be aware the larger you make it > the larger and slower your indexes will be so don't go overboard. > This is based on http://dev.mysql.com/doc/refman/5.6/en/char.html > you will need to check the equivalent documentation page for the exact > version you are running to verify if its supported on your version. > > > On Thu, Feb 26, 2015 at 4:28 AM, Roald <depja...@gmail.com> wrote: > >> mysql 5.5 should have a limit of for varchar of 65553 bytes see : >> http://dev.mysql.com/doc/refman/5.5/en/char.html >> >> So I could possibly try something like this: >> >> ALTER TABLE <table_name> MODIFY <col_name> VARCHAR(10000) >> http://stackoverflow.com/questions/1279568/how-can-i-modify-the-size-of-column-in-a-mysql-table >> >> Now I have to find the table_name and col_name where CustomerIDs is stored. >> >> Regards, >> Roald >> >> >> On Thu, Feb 26, 2015 at 6:50 AM, Roald <depja...@gmail.com> wrote: >> >>> Interesting. So if I would switch to postgresql I would Get double The >>> amount of characters without having to do anything else. 512 characters is >>> still not enough though. >>> >>> Would I have to change any code in OTRS if I would change to blob? where >>> would I find this code? >>> >>> As far as I understand the field CustomerIDs is created by The xml >>> definition so I would probably have to find it in a table related to xml >>> definitions somewhere. Any idea how to find this field? >>> >>> I will try to make a blob out of it and see what happens. >>> >>> Thank you very much, >>> >>> Regards, >>> Roald >>> Op 26 feb. 2015 00:42 schreef <prmari...@gmail.com> het volgende: >>> >>> Sorry it's been a long time since I dug into the schema. Also be aware >>>> if I remember correctly the limitation comes from MySQL. VARCHAR fields in >>>> MySQL max out at 256 characters and PostgreSQL maxes out at 512. This could >>>> in theory be resolved by transforming the column into a "TEXT" field which >>>> is essentially a BLOB containing text, but I don't know how well MySQL with >>>> searches of that field type. I know extensive work was done in PostgreSQL >>>> to make it work well for data warehouses, but I doubt much work was done on >>>> it for MySQL since I last looked. >>>> >>>> Sent from my BlackBerry 10 smartphone. >>>> *From: *Roald >>>> *Sent: *Wednesday, February 25, 2015 13:28 >>>> *To: *Development community of OTRS >>>> *Reply To: *Development community of OTRS >>>> *Subject: *Re: [dev] how to change maxlength of a textarea defined in >>>> an xml file? >>>> >>>> I had a suspicion that I would need to do something like that. >>>> >>>> Would you happen to know how to go about this? >>>> >>>> Thank you very much, >>>> With kind regards, >>>> Roald >>>> Op 25 feb. 2015 18:05 schreef "Paul Robert Marino" <prmari...@gmail.com> >>>> het volgende: >>>> >>>>> for that you would have to alter the database schema. >>>>> >>>>> On Wed, Feb 25, 2015 at 6:12 AM, Roald <depja...@gmail.com> wrote: >>>>> > Dear all, >>>>> > >>>>> > I want to make a small adaption to this CustomerSLA module: >>>>> > http://opar.perl-services.de/package/D/DI/DIETMARB/CustomerSLA >>>>> > >>>>> > I would like to increase the amount of accepted characters of the >>>>> > CustomerIDs field. >>>>> > >>>>> > Step one is to increase the Cols and Rows in >>>>> > /opt/otrs/Kernel/Config/Files/CustomerSLA.xml >>>>> > >>>>> > <ConfigItem Name="SLAPreferences###02_CustomerIDs" Required="0" >>>>> > Valid="1"> >>>>> > <Description Translatable="1">List of customer company IDs >>>>> for which >>>>> > this SLA applies.</Description> >>>>> > <Group>CustomerSLA</Group> >>>>> > <SubGroup>Frontend::SLA::Preferences</SubGroup> >>>>> > <Setting> >>>>> > <Hash> >>>>> > <Item >>>>> > Key="Module">Kernel::Output::HTML::SLAPreferencesGeneric</Item> >>>>> > <Item Key="Label">CustomerIDs</Item> >>>>> > <Item Key="Desc">List of customer company IDs for >>>>> which this >>>>> > SLA applies.</Item> >>>>> > <Item Key="Block">TextArea</Item> >>>>> > <Item Key="Cols">50</Item> >>>>> > <Item Key="Rows">3</Item> >>>>> > <Item Key="PrefKey">CustomerIDs</Item> >>>>> > </Hash> >>>>> > </Setting> >>>>> > </ConfigItem> >>>>> > >>>>> > But If I change Cols and Rows the amount of characters when I hit >>>>> Submit in >>>>> > the AdminCustomerSLA window still gets limited to 250 characters. >>>>> How do I >>>>> > increase the max lenght of characters of CustomerIDs ? >>>>> > >>>>> > Thank you very much, >>>>> > With kind regards. >>>>> > Roald >>>>> > >>>>> > _______________________________________________ >>>>> > OTRS mailing list: dev - Webpage: http://otrs.org/ >>>>> > Archive: http://lists.otrs.org/pipermail/dev >>>>> > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >>>>> _______________________________________________ >>>>> OTRS mailing list: dev - Webpage: http://otrs.org/ >>>>> Archive: http://lists.otrs.org/pipermail/dev >>>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> OTRS mailing list: dev - Webpage: http://otrs.org/ >>>> Archive: http://lists.otrs.org/pipermail/dev >>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >>>> _______________________________________________ >>>> OTRS mailing list: dev - Webpage: http://otrs.org/ >>>> Archive: http://lists.otrs.org/pipermail/dev >>>> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >>>> >>> >> >> _______________________________________________ >> OTRS mailing list: dev - Webpage: http://otrs.org/ >> Archive: http://lists.otrs.org/pipermail/dev >> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >> > > > _______________________________________________ > OTRS mailing list: dev - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/dev > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev >
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
