CopyForce (and CopyStorm -- the commercial variant) does not support MySQL (I have not needed it on a project). This morning I took a look at the effort....the effort looks small. In a couple of hours I was exporting Salesforce data.
A question: Is there enough MySQL interest to make it worth my effort? Please drop me a line if you would be interested in trying it out. If few people respond, I probably will not launch a MySQL version.
Since it is summer and time for outdoor fun, progress on a WAR that provides browser access to CopyForce data has slowed. Though the individual record pages and list of record pages are in place, I will need some concentrated time to bring it to beta state. Maybe this fall.
It's time to take a swim (it's hot outside).
Saturday, July 16, 2011
Friday, July 8, 2011
Limits of SOQL -- SQLForce Solution
One aspect of SOQL that is a bit annoying is its restrictions of where column names can appear in a query. A query I have want to run a few times:
SELECT id FROM Account WHERE ShippingCountry != BillingCountry
Bummer....SOQL does not allow column names on the right side of an expression.
Recently a user reported a bug with SQLForce that is caused by the same SOQL limitation. He report that a SQLForce query like:
UPDATE Account SET ShippingCountry = BillingCountry WHERE ShippingCountry=null
set all ShippingCountry values to the string "BillingCountry." Why? Since SOQL does not have a native UPDATE statement, SQLForce simulates it using a SELECT followed by an Update() call. Since SQLForce knows that SOQL does not allow column names on the right, it assumes that the user forgot to quote a string in the UPDATE statement.
How can this problem be approached in a couple of lines of code. The answer for me is with the SQLForce Jython module. I'll post a typical solution tomorrow.
SELECT id FROM Account WHERE ShippingCountry != BillingCountry
Bummer....SOQL does not allow column names on the right side of an expression.
Recently a user reported a bug with SQLForce that is caused by the same SOQL limitation. He report that a SQLForce query like:
UPDATE Account SET ShippingCountry = BillingCountry WHERE ShippingCountry=null
set all ShippingCountry values to the string "BillingCountry." Why? Since SOQL does not have a native UPDATE statement, SQLForce simulates it using a SELECT followed by an Update() call. Since SQLForce knows that SOQL does not allow column names on the right, it assumes that the user forgot to quote a string in the UPDATE statement.
How can this problem be approached in a couple of lines of code. The answer for me is with the SQLForce Jython module. I'll post a typical solution tomorrow.
Subscribe to:
Posts (Atom)