Changes made in Appery.io

In order to preserve the promise of transparency and open communication, the change log records changes to topics made by both customers and employees. Anyone can dispute a change by clicking the "Dispute" link and entering additional details.


  • April 18, 2016 15:43
    John Black
    Changed reply in topic of API Express, Appery.io Database and $Regex by John Black to Galyna -<br /> <br />So I'm getting conflicting feedback. Evgene says its a bug, you say I'm doing it wrong.<br /> <br />If by manually you mean programmatically, then yes, I'm doing it that way because the value(s) supplied by the user need to be built into the where clause. The ability to do it programmatically becomes even more important when I'm searching a long description field for keywords, i.e.<br /> <br />Keywords entered by user: contact lenses dry<br /> <br />Long description: The following contact lenses are vastly improved over our previous product, reducing dry eyes and eye fatigue.<br /> <br />Those three keywords are concatenated into a where clause with regex and the options i parameter (to ignore case):<br /> <br /><pre><code>whereClause = &#39;{&quot;$and&quot;: [&#39;;&lt;br&gt; &lt;br&gt;&lt;br&gt;&lt;br&gt; var searchTerms = searchtermEntry&#46;split(&#39; &#39;);&lt;br&gt; &#47;&#47; Loop through keywords&lt;br&gt; for(var i = 0; i &lt; searchTerms&#46;length; i++) {&lt;br&gt; &#47;&#47; Trim the excess whitespace&#46;&lt;br&gt; searchTerms[i] = searchTerms[i]&#46;replace(/^\s*/, &quot;&quot;)&#46;replace(/\s*$/, &quot;&quot;);&lt;br&gt; &#47;&#47; Add additional code here, such as:&lt;br&gt; whereClause = whereClause + &#39;{&quot;SearchField&quot;:{&quot;$regex&quot;:&quot;&#39;+searchTerms[i]+&#39;+&quot;, &quot;$options&quot;:&quot;i&quot;}},&#39;;&lt;br&gt; }&lt;br&gt; whereClause = whereClause + &#39;{&quot;EventTypeName&quot;:&quot;Poster&quot;}&#39;;&lt;br&gt; whereClause = whereClause + &#39;]}&#39;;&lt;br&gt; requestData&#46;where = JSON&#46;parse(whereClause);</code></pre><br /> <br />But that's my more complex $regex functional need. For now, I just need to be able to get one "keyword" working with $regex - I can extrapolate it later for my long description search. <br /> <br />My JS code is about as reduced as one could get. I've altered it as follows:<br /> <br /><a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401107/RegexTest1.png?1460993342" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401107/RegexTest1_inline.png?1460993342" /></a><br /> <br /><br />For the above example, I've hard coded the where clause and I'm using your template exactly. I still get the following error:<br /> <br /><a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401110/RegexTestResults1.png?1460993373" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401110/RegexTestResults1_inline.png?1460993373" /></a><br /> <br />If I modify it further, just for testing purposes, to the following to match your reduced template:<br /> <br /><a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401111/RegexTest2.png?1460993397" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401111/RegexTest2_inline.png?1460993397" /></a><br /> <br />I get the following:<br /> <br /><a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401112/RegexTestResults2.png?1460993415" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401112/RegexTestResults2_inline.png?1460993415" /></a><br /> <br />So neither of your examples work for me. Did the develoeprs who created these examples run them through an API Express connection to an Appery.io database?<br /> <br />You tell me I'm doing it wrong but don't exactly say what about my JS code is wrong. Is it the JSON.parse command? Is it the syntax of the where clause? This code works when using the REST service with the Appery.io database. \ It only fails when using the API Express service to the same database.<br /> <br />JS code -&gt; Appery.io Database via REST -&gt; Correct data returned<br /> JS code -&gt; Appery.io Database via API Express -&gt; Error returned<br /> <br />Your example templates are static - I understand they are that way for basic testing but I can't keep them that way. I need to be able to Programmatically generate the where clause. Using the mapping button doesn't work for me because it can be a many to one relationship between the values entered and the field to search against.<br /> <br />As a side note, your example doesn't utilize the $options parameter with $regex - is that no longer valid? For searching long description fields, I need to be able to ignore case. I'm hoping the $options just wasn't used in the examples..
  • April 18, 2016 15:41
    John Black
    Changed reply in topic of API Express, Appery.io Database and $Regex by John Black to Galyna - <br /><br /> So I'm getting conflicting feedback. Evgene says its a bug, you say I'm doing it wrong. <br /><br /> If by manually you mean programmatically, then yes, I'm doing it that way because the value(s) supplied by the user need to be built into the where clause. The ability to do it programmatically becomes even more important when I'm searching a long description field for keywords, i.e. <br /><br /> Keywords entered by user: contact lenses dry <br /><br /> Long description: The following contact lenses are vastly improved over our previous product, reducing dry eyes and eye fatigue. <br /><br /> Those three keywords are concatenated into a where clause with regex and the options i parameter (to ignore case): <br /><br /> <pre><code>whereClause = &#39;{&quot;$and&quot;: [&#39;; &lt;br&gt;&lt;br&gt; var searchTerms = searchtermEntry&#46;split(&#39; &#39;); &lt;br&gt;&lt;br&gt; &#47;&#47; Loop through keywords &lt;br&gt; for(var i = 0; i &lt; searchTerms&#46;length; i++) { &lt;br&gt; &#47;&#47; Trim the excess whitespace&#46; &lt;br&gt; searchTerms[i] = searchTerms[i]&#46;replace(/^\s*/, &quot;&quot;)&#46;replace(/\s*$/, &quot;&quot;); &lt;br&gt;&lt;br&gt; &#47;&#47; Add additional code here, such as: &lt;br&gt; whereClause = whereClause + &#39;{&quot;SearchField&quot;:{&quot;$regex&quot;:&quot;&#39;+searchTerms[i]+&#39;+&quot;, &quot;$options&quot;:&quot;i&quot;}},&#39;; &lt;br&gt;&lt;br&gt; } &lt;br&gt;&lt;br&gt; whereClause = whereClause + &#39;{&quot;EventTypeName&quot;:&quot;Poster&quot;}&#39;; &lt;br&gt; whereClause = whereClause + &#39;]}&#39;; &lt;br&gt;&lt;br&gt; requestData&#46;where = JSON&#46;parse(whereClause);</code></pre> <br /><br /> But that's my more complex $regex functional need. For now, I just need to be able to get one "keyword" working with $regex - I can extrapolate it later for my long description search. <br /><br /> My JS code is about as reduced as one could get. I've altered it as follows: <br /><br /> <a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401107/RegexTest1.png?1460993342" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401107/RegexTest1_inline.png?1460993342" /></a> <br /><br /> For the above example, I've hard coded the where clause and I'm using your template exactly. I still get the following error: <br /><br /> <a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401110/RegexTestResults1.png?1460993373" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401110/RegexTestResults1_inline.png?1460993373" /></a> <br /><br /> If I modify it further, just for testing purposes, to the following to match your reduced template: <br /><br /> <a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401111/RegexTest2.png?1460993397" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401111/RegexTest2_inline.png?1460993397" /></a> <br /><br /> I get the following: <br /><br /> <a href="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401112/RegexTestResults2.png?1460993415" rel="nofollow"><img alt="" src="https://d2r1vs3d9006ap.cloudfront.net/s3_images/1401112/RegexTestResults2_inline.png?1460993415" /></a> <br /><br /> So neither of your examples work for me. Did the develoeprs who created these examples run them through an API Express connection to an Appery.io database? <br /><br /> You tell me I'm doing it wrong but don't exactly say what about my JS code is wrong. Is it the JSON.parse command? Is it the syntax of the where clause? This code works when using the REST service with the Appery.io database. \ It only fails when using the API Express service to the same database. <br /><br /> JS code -&gt; Appery.io Database via REST -&gt; Correct data returned <br /> JS code -&gt; Appery.io Database via API Express -&gt; Error returned <br /><br /> Your example templates are static - I understand they are that way for basic testing but I can't keep them that way. I need to be able to Programmatically generate the where clause. Using the mapping button doesn't work for me because it can be a many to one relationship between the values entered and the field to search against. <br /><br /> As a side note, your example doesn't utilize the $options parameter with $regex - is that no longer valid? For searching long description fields, I need to be able to ignore case. I'm hoping the $options just wasn't used in the examples. .
  • April 18, 2016 14:03
    Black Angel, the poster:
    Removed a reply by Black Angel in if condition
    Reason: User-initiated delete from community
  • April 18, 2016 09:48
    Black Angel, the poster:
    Reason: removed by the poster
  • April 17, 2016 21:06
    Black Angel, the poster:
    Reason: removed by the poster
  • April 17, 2016 16:57
    Illya Stepanov Dispute this change
  • April 17, 2016 05:33
    Illya Stepanov Dispute this change
  • April 15, 2016 18:08
    Black Angel, the poster:
    Reason: removed by the poster
  • April 15, 2016 18:08
    Black Angel, the poster:
    Reason: removed by the poster
  • April 15, 2016 18:07
    Black Angel, the poster:
    Reason: removed by the poster
  • April 15, 2016 13:17
    Illya Stepanov Dispute this change
  • April 15, 2016 12:01
    Black Angel, the poster:
    Reason: removed by the poster
  • April 15, 2016 10:16
    Illya Stepanov Dispute this change
  • April 14, 2016 11:52
    Andy Parker, the poster:
    Reason: User-initiated delete from community
  • April 12, 2016 15:37
    frustrateddeveloper, the poster:
    Reason: removed by the poster
  • April 12, 2016 08:39
    Dave Barraclough, the poster:
    Reason: removed by the poster
  • April 11, 2016 13:08
    Vinny B, the poster:
    Removed site down? by Vinny B
    Reason: removed by the poster
  • April 11, 2016 11:43
    Mark Wong, the poster:
    Reason: removed by the poster
  • April 11, 2016 06:25
    Mark Wong, the poster:
    Reason: removed by the poster
  • April 10, 2016 11:07
    Illya Stepanov
next » « previous