1
0
-1

Hi team,

I am running into problems when moving data from Joget into databases that require the unique identifier to be compliant with UUIDv4 / RFC (for example MS SQL uniqueidentifier column).

Would it be possible to give the option at app or system level to switch between how the UUID is generated? For example the UUID service could use the java standard instead:

 

import java.util.UUID;

UUID uuid = UUID.randomUUID();

return uuid.toString();

Cheers,

Eric

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Hi HugoOwen Ong and team, any ideas for this one?

      Building in the switch would be great (assuming the changes would have to be made in the settings UI and UUID service?).

      Cheers,

      Eric

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Hi, do you need to use a column type like uniqueidentifier? It would work fine in MS SQL if you just use varchar.

        1. Eric

          Hi Anders, I fear we have to as other systems rely on the uniqueidentifier type and we need the performance efficiency with large tables. I can use beanshell hash variables with the code above in some cases but it becomes painful to customize everywhere. Looking at the community version github code it seems a switch between the proprietary id algorithm and java standard should be doable?

        CommentAdd your comment...