Changeset 33419 in project


Ignore:
Timestamp:
06/14/16 04:36:11 (3 years ago)
Author:
svnwiki
Message:

Anonymous wiki edit for IP [45.79.100.212]:

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/dbi

    r9103 r33419  
    77These functions should be optimized for speed.
    88
    9 ; <procedure>(dbi:connect TYPE #!key FILE PORT USER PASS etc)</procedure> : Connect to a database. TYPE is a symbol, like mysql, postgres, sqlite, etc. Returns a connection object.
     9<procedure>(dbi:connect TYPE #!key FILE PORT USER PASS etc)</procedure>
     10 Connect to a database. TYPE is a symbol, like mysql, postgres, sqlite, etc. Returns a connection object.
    1011''Possibly put the type, file, and port info into a URI-type string as JDBC does? That would make
    1112the whole thing a lot more extensible; it would be nice to do it both ways, having the separate keyword parameters also. -- vincent''
    1213
    13 ; <procedure>(dbi:query CONNECTION SQL)</procedure> : Query the database (see the mysql egg)
     14<procedure>(dbi:query CONNECTION SQL)</procedure>
     15 Query the database (see the mysql egg)
    1416
    15 ; <procedure>(dbi:num-rows CONNECTION)</procedure> : Return the number of rows produced by the last query (see mysql)
     17<procedure>(dbi:num-rows CONNECTION)</procedure>
     18 Return the number of rows produced by the last query (see mysql)
    1619
    17 ; <procedure>(dbi:fetch-row CONNECTION)</procedure> : Return the next row (see mysql).
     20<procedure>(dbi:fetch-row CONNECTION)</procedure>
     21 Return the next row (see mysql).
    1822
    19 ; <procedure>(dbi:insert-id CONNECTION)</procedure> : Returns the ID generated by the last insert statement.
     23<procedure>(dbi:insert-id CONNECTION)</procedure>
     24 Returns the ID generated by the last insert statement.
    2025
    2126''I'd like to see support for prepared statements. Especially in transactional environments, on some
     
    2732These functions should be optimized for convenience in i.e. quick and dirty scripts. Perhaps these types of functions should be their own library on top of DBI? Perhaps there are even more convenient functions we could have?
    2833
    29 ; <procedure>(dbi:query-list CONNECTION SQL)</procedure> : Returns a list of result rows.
     34<procedure>(dbi:query-list CONNECTION SQL)</procedure>
     35 Returns a list of result rows.
    3036
    31 ; <procedure>(dbi:query-fold CONNECTION PROC SQL SEED)</procedure> : fold
     37<procedure>(dbi:query-fold CONNECTION PROC SQL SEED)</procedure>
     38 fold
    3239
    33 ; <procedure>(dbi:query-map CONNECTION PROC SQL)</procedure> : map
     40<procedure>(dbi:query-map CONNECTION PROC SQL)</procedure>
     41 map
    3442
    35 ; <procedure>(dbi:query-for-each CONNECTION PROC SQL SEED)</procedure> : for-each
     43<procedure>(dbi:query-for-each CONNECTION PROC SQL SEED)</procedure>
     44 for-each
    3645
    3746==== Stream Functions
    3847
    39 ; <procedure>(dbi:query-stream CONNECTION SQL)</procedure> : Return an SRFI-40/SRFI-41 stream of rows.
     48<procedure>(dbi:query-stream CONNECTION SQL)</procedure>
     49 Return an SRFI-40/SRFI-41 stream of rows.
    4050
    4151
Note: See TracChangeset for help on using the changeset viewer.