This component provides a system for automatically storing modified 4D methods. Every change of a method, whether a project, object, form or database method, is automatically stored in a table, either of the local database or a 4D Server.
Download Complete Tech Note and Example:Windows | Mac
Commented by Chris Visaya on May 10, 2010 at 2:57 PM
Hi Chris Norman,
In this situation, the best thing to do is contact the Tech Support team who will be happy to investigate the issue. They will address any bugs that they find along the way.
Kind Regards, Chris Visaya
Commented by Chris Norman on May 4, 2010 at 3:58 PM
This component "broke" when we moved to v11.6 Hotfix 1. It seems to be in the syntax of the SQL used via ODBC connection in the method MethodHistory_ReadHistory.
The following two code snippets now produce different results:
SELECT id FROM SomeTable
WHERE id=1 AND name="joe"
INTO :array_of_ids
Fills the array with IDs from every row of SomeTable (i.e. WHERE clause is ignored). In this case:
SELECT id FROM SomeTable
WHERE id=1
AND name="joe"
INTO :array_of_ids
fills the array with just one element, as expected.
So whitespace matters in the WHERE clause?
Commented by Jesse Pina on May 8, 2009 at 9:47 AM
While the main focus of this tech note is comparing two different versions of methods, the "diff" functionality used in this tech note can be useful for comparing any text.
In this situation, the best thing to do is contact the Tech Support team who will be happy to investigate the issue. They will address any bugs that they find along the way.
Kind Regards,
Chris Visaya
The following two code snippets now produce different results:
SELECT id FROM SomeTable
WHERE id=1 AND name="joe"
INTO :array_of_ids
Fills the array with IDs from every row of SomeTable (i.e. WHERE clause is ignored). In this case:
SELECT id FROM SomeTable
WHERE id=1
AND name="joe"
INTO :array_of_ids
fills the array with just one element, as expected.
So whitespace matters in the WHERE clause?