JA Job Board Component 8,554 posts

[sooraj Friend soorajJoin date: August 2013Posts: 7Downloads:0Uploads:0 Thanks: 2]

#190254

Hello i have a huge problem…

i’m making my RESUME FORM fields in the JA Job Board…

i have many fields (over 100) and in some time the DATABASE couldn’t be rebuild again (error)…

since mysql has NO field limitation by number but by ROW SIZE (depended on the fields of the table)
.. i run over to DB to see what is happening……

and i was amazed seeing that all fields (textfields) where varchar(255)….
logic i would say since the “field’s creation form” has NO “field length option…)
so fields like name, surname and any other textfields are FORCED to be 255 character which is unacceptable…

i think an extra field param should be added defining the field’s length in the TABLE..

and watch out! SEPERATOR fields should be for example varchar(1) or something… since you decided to be column these too.. (can’t figure out why…)

thanks!

[HeR0 Friend HeR0Join date: August 2011Posts: 3626Downloads:0Uploads:61 Thanks: 33 Thanked: 588 times in 549 posts]

#504502

Hi Sooraj ,

Yes, it is MySQL limit. Please try to edit the length of the fields manuallly.

<blockquote>and i was amazed seeing that all fields (textfields) where varchar(255)….
logic i would say since the “field’s creation form” has NO “field length option…)
so fields like name, surname and any other textfields are FORCED to be 255 character which is unacceptable…</blockquote> Reducing size is not the best solution and we will try to update this in future.

Regards

[sooraj Friend soorajJoin date: August 2013Posts: 7Downloads:0Uploads:0 Thanks: 2]

#504534

<em>@HeR0 387826 wrote:</em><blockquote>Hi Sooraj ,

Yes, it is MySQL limit. Please try to edit the length of the fields manuallly.

Reducing size is not the best solution and we will try to update this in future.

Regards</blockquote>

ok … i resized my self …(in the mean time) , but thanks for anwsering!
one small issue again with DB..
.
in #__ja_form_fields the field “field_ordering” is TINYINT(4)… this means that the field can be -127 to +127 with sign…so in my resume i have more than 127 fields and every field above No 127 get’s the same ordering!!
i fixed this by simply altering the table’s field ‘field_ordering’ to int(11) ** with no data loss

maybe this could be arranged in new version too!

best regards,

christopher

[HeR0 Friend HeR0Join date: August 2011Posts: 3626Downloads:0Uploads:61 Thanks: 33 Thanked: 588 times in 549 posts]

#505200

Yes, but this might cause the confusion for some guys who are not developer. In fact, a registration form should nothave too much fields.

[Author]

Posts