Bizarre Error Message

A simple SQL statement is throwing an error

Try removing LIMIT 10 which should then allow you to use the simple interface. You can always add it back in later.

Jamie

It seems to be a bug. It is a simple query. Removing the LIMIT then how am I to use the default options of the repeat region?

the default setting is 1 (which returns 1 record) but you can change it to 0 (all records) or specify the number of records you want to return just by changing in code view the value shown after the database connection reference within the recordset manually:

example for all records:

<?php
$Gallery = new WA_MySQLi_RS("Gallery",$DBConnection,0);
$Gallery->setQuery("SELECT * FROM gallery");
$Gallery->execute();
?>

example for 1 record:

<?php
$Gallery = new WA_MySQLi_RS("Gallery",$DBConnection,1);
$Gallery->setQuery("SELECT * FROM gallery");
$Gallery->execute();
?>

example for 10 recrods:

<?php
$Gallery = new WA_MySQLi_RS("Gallery",$DBConnection,10);
$Gallery->setQuery("SELECT * FROM gallery");
$Gallery->execute();
?>

So you can see that it is very easy to add that back in if you remove the LIMIT from the query within the recordset snapin.

But will I then get the warning punctuation mark on the Server Behavior panel? Then will I get the error message again when I try 'Simple' again? If so...as a Senior Software QA, I feel this is a bug. It's your software, you can do what you want with it.

Jamie is a user trying to help. It isn't his software, or at least he isn't someone that works on it. He is just a helpful user trying to help you do what you want and get around your issue.

The simple recordset syntax only works with very simple SQL statements. Once you add a repeat region to your page, it adds a LIMIT statement which complicates your recordset.

You can simplify your recordset by removing the ORDER BY manually as he suggests. Then you can add it back after making your edits in the simple recordset editor.

What changes are you looking to make?

Sounds like it is by design. I would have not expected that behavior. A learning curve on my part. Thanks for the help Jamie.