It makes no sense to "put a print inside another print". PRINT is not an SQL
statement. It is not used to query the database; instead it simply returns a
message, usually a user-defined string, to the client. Most developers use
the PRINT statement for testing/ debugging.
Re: DBMS and lisp, etc. ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database.... (eq (order-customer orderA) ... (comp.lang.lisp)
Re: complex filter and calculations in access ... switch to SQL view. ...query by switching to datasheet view, ... of your database using the from address in this post. ...pre-op infections yes/no ... (microsoft.public.access.queries)
Re: A little more meat this week ... implementation with a query processor capable of returning a result set ... then we can call it a result bag (SQL... I'm looking at the data model and not database tools at this ... for a s/w developer and a s/w developer simplifies for the end user). ... (comp.databases.pick)
Re: complex filter and calculations in access ... when using a subquery on the same table as the main query, ...switch to SQL view. ... of your database using the from address in this post. ... (microsoft.public.access.queries)
Re: A little more meat this week ... said data includes lists."... implementation with a query processor capable of returning a result set ... then we can call it a result bag (SQL... I'm looking at the data model and not database tools at this ... (comp.databases.pick)
