I'm still using the Kony 7.3 Mobile platform to build mobile apps that sync data with a backend SQL server.

And, I know that I can alter/modify the SQL query generated by the Kony 7.3 sync server, that will be run against the backend SQL Server, by adding relations and filters (for example in the XML sync definition files).

My current interrogation is about modifying the type of the input parameters of this generated query.

A typical generated query will be :

` DECLARE @P0 bigint = 15343805141, @P1 bigint = 15358042711;

SELECT TOP 100
    [MyTable].[Id],
    [MyTable].[MyColumnA],
    [MyTable].[MyColumnB],
    [MyTable].[MyStatusFlag],      --> The SoftDeleteFlagAttribute in the XML definition of the sync
    [MyTable].[MySyncTimestamp]    --> The UpdateTimeStampAttribute in the XML definition of the sync
FROM [MySchema].[MyTable]
WHERE [MyTable].[MySyncTimestamp] > @P0 
      AND [MyTable].[MySyncTimestamp] <= @P1;`

We've just found out that if we could use instead the corresponding timestamp values of the parameters @P0 and @P1 (see the query below), the generated query with be executed with better performance on the backend SQL Server.

` DECLARE @P0 timestamp = 0x0000000392C8D9DD, @P1 timestamp = 0x000000039353EF99;

SELECT TOP 100
    [MyTable].[Id],
    [MyTable].[MyColumnA],
    [MyTable].[MyColumnB],
    [MyTable].[MyStatusFlag],      --> The SoftDeleteFlagAttribute in the XML definition of the sync
    [MyTable].[MySyncTimestamp]    --> The UpdateTimeStampAttribute in the XML definition of the sync
FROM [MySchema].[MyTable]
WHERE [MyTable].[MySyncTimestamp] > @P0 
      AND [MyTable].[MySyncTimestamp] <= @P1;`

Question, is there a way to perform this kind of hacks?

Cordially, Hervé N.