Differences

This shows you the differences between two versions of the page.

--- developers:geoclass:geotransaction:start [2009/06/09 19:28]
jonyo wording
+++ developers:geoclass:geotransaction:start [2014/09/25 16:55] (current)
@@ Line 21: / Line 21: @@
 ==== Common Pitfalls: ====
-**Max length is 255**:  If a gateway needs a longer ID length, store the first 255 chars using setGatewayTransaction() for faster and easier "lookup" of the transaction.  But then store the full ID in the transaction's registry.  See the code snipped further below for an example of how to code for it.
+**Max length is 255**:  If a gateway needs a longer ID length, store the first 255 chars using setGatewayTransaction() for faster and easier "lookup" of the transaction.  But then store the full ID in the transaction's registry.  See the code snippet further below for an example of how to code for it.
 **ID Cannot be numeric**:  If the ID passed into geoTransaction::getTransaction($id) is numeric, it only looks up transactions with that ID as the internal ID.  So if the "gateway transaction ID" is numeric, the transaction will not be found when you try to use geoTransaction::getTransaction($id), unless you add a string to it to ensure it is not numeric.  See the code snippet below for an example of how to code for this:

Geodesic Solutions Community Wiki