headers
David Thole | 3 Mar 2012 00:31
Picon

Duplicate results from query

Hey all,


I'm running into a bit of an issue, that I'm unsure of what's going on.

Essentially the code I'm writing is located here:

The backend is sqlite3.  The database table has 3 entries, yet the query is returning 6 entries total.   I tracked this down, to what appears, to be the the (:retrieval :immediate) portion of the database definition.  If I don't do an immediate on these, it doesn't return 6, but instead 3 (like it should).  it seems that the immediate retrieval is the issue.

I'm currently using the latest version of clsql through quicklisp.

Does anyone know if I'm doing something obviously incorrect here? My google searches haven't found much to help point me to the issue.

Thanks

- David
_______________________________________________
CLSQL mailing list
CLSQL@...
http://lists.b9.com/cgi-bin/mailman/listinfo/clsql
Permalink | Reply |
headers
Ryan Davis | 5 Mar 2012 15:11
Favicon
Gravatar

Re: Duplicate results from query

Try using clsql:start-sql-recording to see exactly what query clsql is running, you might be getting a cross-join by accident. See http://clsql.b9.com/manual/start-sql-recording.html for more information.

Thanks,
Ryan Davis Acceleration.net Director of Programming Services 2831 NW 41st street, suite B Gainesville, FL 32606 Office: 352-335-6500 x 124 Fax: 352-335-6506
On 3/2/2012 6:31 PM, David Thole wrote:
Hey all,

I'm running into a bit of an issue, that I'm unsure of what's going on.

Essentially the code I'm writing is located here:

The backend is sqlite3.  The database table has 3 entries, yet the query is returning 6 entries total.   I tracked this down, to what appears, to be the the (:retrieval :immediate) portion of the database definition.  If I don't do an immediate on these, it doesn't return 6, but instead 3 (like it should).  it seems that the immediate retrieval is the issue.

I'm currently using the latest version of clsql through quicklisp.

Does anyone know if I'm doing something obviously incorrect here? My google searches haven't found much to help point me to the issue.

Thanks

- David


_______________________________________________ CLSQL mailing list CLSQL-0lovp2JerKU@public.gmane.org http://lists.b9.com/cgi-bin/mailman/listinfo/clsql 
_______________________________________________
CLSQL mailing list
CLSQL@...
http://lists.b9.com/cgi-bin/mailman/listinfo/clsql
Permalink | Reply |

Gmane