[Haddock docs html update. alistair@abayley.org**20060711152038] { hunk ./doc/html/Database-Enumerator.html 885 - execDDL "create table blah" - execDML "insert into blah ..." + execDDL (sql "create table blah") + execDML (sql "insert into blah ...") hunk ./doc/html/Database-Enumerator.html 891 - execDML "update blah ..." - execDML "insert into blah ..." + execDML (sql "update blah ...") + execDML (sql "insert into blah ...") hunk ./doc/html/Database-Enumerator.html 1033 ->A longer explanation of bind variables is in the Bind Parametes section below. +>A longer explanation of bind variables is in the Bind Parameters section below. hunk ./doc/html/Database-Enumerator.html 1079 - with the new value of the accumulator/seed returned. + returning the wrapped accumulator/seed value. hunk ./doc/html/Database-Enumerator.html 1083 - begin fed to the iteratee function, along with the new accumulator/seed. + begin fed to the iteratee function, along with the new accumulator/seed value. hunk ./doc/html/Database-Enumerator.html 1095 - Consing the rows to the front of the list results in a list that is the result set + Consing the rows to the front of the list results in a list hunk ./doc/html/Database-Enumerator.html 1125 - By directly support we mean there is type-specific marshalling code - implemented. - is often, but not always, supported. +> is often, but not always, supported.) hunk ./doc/html/Database-Enumerator.html 1132 ->Indirect support for By directly support we mean there is type-specific marshalling code + implemented. + Indirect support for becomes: +>reduces (with use of IterAct and IterResult) to: hunk ./doc/html/Database-Enumerator.html 1273 - for returning values from iteratee functions. The return type from an interatee is actually + for returning values from iteratee functions. The return type from an iteratee is actually hunk ./doc/html/Database-Enumerator.html 1386 - is an instance of the Statement class, so it can be passed to - Statement class, + so it can be passed to Assuming we have these functions in the database: +>Again for PostgreSQL, assuming we have these functions in the database: hunk ./doc/html/Database-Enumerator.html 1741 ->... then this code shows how nested queries mights work in PostgreSQL: +>... then this code shows how nested queries mights work: hunk ./doc/html/Database-Enumerator.html 1771 - here we use mapM_ to apply an IO action to the list returned by + here we use mapM_ to apply an IO action to the list returned by hunk ./doc/html/Database-Enumerator.html 2632 +>This is really just a wrapper that lets us write lists of + heterogenous bind values e.g. [bindP string, bindP (0::Int), ...] +This is really just a wrapper that lets us write lists of + heterogenous bind values e.g. [bindP string, bindP (0::Int), ...] +prefetch :: Int -> String -> QueryStringTunedsql_tuned :: QueryResourceUsage -> String -> QueryStringTunedprefetch :: Int -> String -> QueryStringTunedsql_tuned :: QueryResourceUsage -> String -> QueryStringTunedInvoke main like this (assuming compiled to takusen.exe): +>Invoke main like this (assuming the compiled executable is called takusen): hunk ./doc/html/Test-MiniUnit.html 87 ->exposed for self-testing only; see MiniUnitTestExposed for self-testing only; see Test.MiniUnitTestHUnitTest.HUnitTest.HUnit + to use exposed for self-testing only; see MiniUnitTestExposed for self-testing only; see Test.MiniUnitTest4 (Function)Database.Stub.Enumeratorsql_tunedDatabase.Stub.Enumerator