dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Edward,

on second thought.. This could easily be fixed by making sure that uids for
categories (dataelementcategory table) do not start with a digit, rather a
letter. It is only categories, data element group sets and organisation
unit group sets that can act as dynamic data dimensions. In 2.12 we
introduced categories as dimensions. Since it worked with 2.11, it means
that you have one or more categories starting with a digit - simply correct
these and try again. It will not be necessary to correct all of the data
element uids for this purpose since they never act as table columns.

Lars


On Wed, Jun 19, 2013 at 11:54 AM, Lars Helge Øverland
<larshelge@xxxxxxxxx>wrote:

> Hi Alex and Edward,
>
> let me see if I can provide a fix for this issue, will get back to you.
>
> Lars
>
>
>
> On Wed, Jun 19, 2013 at 9:27 AM, Alex Tumwesigye <atumwesigye@xxxxxxxxx>wrote:
>
>> Lars,
>>
>> Then I guess we are in trouble.
>> This bug becomes a problem when we upgrade to version 2.12.
>> For version 2.11, we have not big issues!
>>
>> --
>> You received this bug notification because you are a member of DHIS 2
>> developers, which is subscribed to DHIS.
>> https://bugs.launchpad.net/bugs/1191698
>>
>> Title:
>>   Analytics creation causes SQL syntax error
>>
>> Status in DHIS 2 - District Health Information Software:
>>   New
>>
>> Bug description:
>>   The analytics tables use DHIS2 UIDs as fieldnames in a number of
>>   tables. However the rules for a table column's name are restricted by
>>   the rules for any identifiers in the SQL language.  Namely:
>>
>>   - Identifiers  and key words must begin with a letter or an underscore.
>> Subsequent characters in an identifier or key word can be letters,
>> underscores, digits (0-9), or dollar signs ($)
>>   - Quoted identifiers can contain any character, except the character
>> with code zero. (To include a double quote, write two double quotes.) This
>> allows constructing table or column names that would otherwise not be
>> possible, such as ones containing spaces or ampersands
>>
>>   The SQL generated during the analytics creation process uses unquoted
>>   identifiers and therefore any UID involved that starts with a digit
>>   will cause a syntax error.
>>
>>   There are two possible solutions to this problem:
>>
>>   1) Add quotes to to all identifiers.
>>   2) Prefix UID derived identifiers with a compatible fixed string like
>> "UID" ("5AfiAeRLQkm" => "UID5AfiAeRLQkm")
>>
>>   The choice of route will depend on how difficult it is to change. If
>>   all we require to quote identifiers is modifying an ORM setting then
>>   route 1 is the obvious choice.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/dhis2/+bug/1191698/+subscriptions
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>