- 浏览: 178841 次
- 来自: ...
文章分类
最新评论
-
fsword:
同事拿着试了一下,说是把第五步放到第二步之前就可以了
在windows下安装ruby1.9.2,rails3.0.3和DevKit--转 -
dothwinds:
[flash=200,200][/flash][url][/u ...
打包ruby or rails成exe(英文)
SQLite/Ruby FAQ
- How do I do a database query?
- How do I prepare a statement for repeated execution?
- How do I use placeholders in an SQL statement?
- How do I discover metadata about a query?
- I’d like the rows to be indexible by column name.
- I’d like the values from a query to be the correct types, instead of String.
- How do insert binary data into the database?
- How do I do a DDL (insert, update, delete) statement?
- How do I execute multiple statements in a single string?
- How do I begin/end a transaction?
Use the Database#execute method. If you don’t give it a block, it will return an array of all the rows:
require 'sqlite3' db = SQLite3::Database.new( "test.db" ) rows = db.execute( "select * from test" )
Use the Database#execute method. If you give it a block, each row of the result will be yielded to the block:
require 'sqlite3' db = SQLite3::Database.new( "test.db" ) db.execute( "select * from test" ) do |row| ... end
Use the Database#execute2 method. This works just like Database#execute; if you don’t give it a block, it returns an array of rows; otherwise, it will yield each row to the block. However, the first row returned is always an array of the column names from the query:
require 'sqlite3' db = SQLite3::Database.new( "test.db" ) columns, *rows = db.execute2( "select * from test" ) # or use a block: columns = nil db.execute2( "select * from test" ) do |row| if columns.nil? columns = row else # process row end end
Easy. Just call Database#get_first_row:
row = db.get_first_row( "select * from table" )
This also supports bind variables, just like Database#execute and friends.
Also easy. Just call Database#get_first_value:
count = db.get_first_value( "select count(*) from table" )
This also supports bind variables, just like Database#execute and friends.
If the same statement is going to be executed repeatedly, you can speed things up a bit by preparing the statement. You do this via the Database#prepare method. It returns a Statement object, and you can then invoke #execute on that to get the ResultSet:
stmt = db.prepare( "select * from person" ) 1000.times do stmt.execute do |result| ... end end stmt.close # or, use a block db.prepare( "select * from person" ) do |stmt| 1000.times do stmt.execute do |result| ... end end end
This is made more useful by the ability to bind variables to placeholders via the Statement#bind_param and Statement#bind_params methods. (See the next FAQ for details.)
Placeholders in an SQL statement take any of the following formats:
-
?
-
?nnn
-
:word
Where n is an integer, and word is an alpha-numeric identifier (or number). When the placeholder is associated with a number, that number identifies the index of the bind variable to replace it with. When it is an identifier, it identifies the name of the correponding bind variable. (In the instance of the first format—a single question mark—the placeholder is assigned a number one greater than the last index used, or 1 if it is the first.)
For example, here is a query using these placeholder formats:
select * from table where ( c = ?2 or c = ? ) and d = :name and e = :1
This defines 5 different placeholders: 1, 2, 3, and “name”.
You replace these placeholders by binding them to values. This can be accomplished in a variety of ways.
The Database#execute, and Database#execute2 methods all accept additional arguments following the SQL statement. These arguments are assumed to be bind parameters, and they are bound (positionally) to their corresponding placeholders:
db.execute( "select * from table where a = ? and b = ?", "hello", "world" )
The above would replace the first question mark with ‘hello’ and the second with ‘world’. If the placeholders have an explicit index given, they will be replaced with the bind parameter at that index (1-based).
If a Hash is given as a bind parameter, then its key/value pairs are bound to the placeholders. This is how you bind by name:
db.execute( "select * from table where a = :name and b = :value", "name" => "bob", "value" => "priceless" )
You can also bind explicitly using the Statement object itself. Just pass additional parameters to the Statement#execute statement:
db.prepare( "select * from table where a = :name and b = ?" ) do |stmt| stmt.execute "value", "name" => "bob" end
Or do a Database#prepare to get the Statement, and then use either Statement#bind_param or Statement#bind_params:
stmt = db.prepare( "select * from table where a = :name and b = ?" ) stmt.bind_param( "name", "bob" ) stmt.bind_param( 1, "value" ) # or stmt.bind_params( "value", "name" => "bob" )
If you ever want to know the names or types of the columns in a result set, you can do it in several ways.
The first way is to ask the row object itself. Each row will have a property “fields” that returns an array of the column names. The row will also have a property “types” that returns an array of the column types:
rows = db.execute( "select * from table" ) p rows[0].fields p rows[0].types
Obviously, this approach requires you to execute a statement that actually returns data. If you don’t know if the statement will return any rows, but you still need the metadata, you can use Database#query and ask the ResultSet object itself:
db.query( "select * from table" ) do |result| p result.columns p result.types ... end
Lastly, you can use Database#prepare and ask the Statement object what the metadata are:
stmt = db.prepare( "select * from table" ) p stmt.columns p stmt.types
By default, each row from a query is returned as an Array of values. This means that you can only obtain values by their index. Sometimes, however, you would like to obtain values by their column name.
The first way to do this is to set the Database property “results_as_hash” to true. If you do this, then all rows will be returned as Hash objects, with the column names as the keys. (In this case, the “fields” property is unavailable on the row, although the “types” property remains.)
db.results_as_hash = true db.execute( "select * from table" ) do |row| p row['column1'] p row['column2'] end
The other way is to use Ara Howard’s ArrayFields module. Just require “arrayfields”, and all of your rows will be indexable by column name, even though they are still arrays!
require 'arrayfields' ... db.execute( "select * from table" ) do |row| p row[0] == row['column1'] p row[1] == row['column2'] end
You can turn on “type translation” by setting Database#type_translation to true:
db.type_translation = true db.execute( "select * from table" ) do |row| p row end
By doing this, each return value for each row will be translated to its correct type, based on its declared column type.
You can even declare your own translation routines, if (for example) you are using an SQL type that is not handled by default:
# assume "objects" table has the following schema: # create table objects ( # name varchar2(20), # thing object # ) db.type_translation = true db.translator.add_translator( "object" ) do |type, value| db.decode( value ) end h = { :one=>:two, "three"=>"four", 5=>6 } dump = db.encode( h ) db.execute( "insert into objects values ( ?, ? )", "bob", dump ) obj = db.get_first_value( "select thing from objects where name='bob'" ) p obj == h
Use blobs. Blobs are new features of SQLite3. You have to use bind variables to make it work:
db.execute( "insert into foo ( ?, ? )", SQLite3::Blob.new( "\0\1\2\3\4\5" ), SQLite3::Blob.new( "a\0b\0c\0d ) )
The blob values must be indicated explicitly by binding each parameter to a value of type SQLite3::Blob.
You can actually do inserts, updates, and deletes in exactly the same way as selects, but in general the Database#execute method will be most convenient:
db.execute( "insert into table values ( ?, ? )", *bind_vars )
The standard query methods (Database#execute, Database#execute2, Database#query, and Statement#execute) will only execute the first statement in the string that is given to them. Thus, if you have a string with multiple SQL statements, each separated by a string, you can’t use those methods to execute them all at once.
Instead, use Database#execute_batch:
sql = <<SQL create table the_table ( a varchar2(30), b varchar2(30) ); insert into the_table values ( 'one', 'two' ); insert into the_table values ( 'three', 'four' ); insert into the_table values ( 'five', 'six' ); SQL db.execute_batch( sql )
Unlike the other query methods, Database#execute_batch accepts no block. It will also only ever return nil. Thus, it is really only suitable for batch processing of DDL statements.
Use Database#transaction to start a transaction. If you give it a block, the block will be automatically committed at the end of the block, unless an exception was raised, in which case the transaction will be rolled back. (Never explicitly call Database#commit or Database#rollback inside of a transaction block—you’ll get errors when the block terminates!)
database.transaction do |db| db.execute( "insert into table values ( 'a', 'b', 'c' )" ) ... end
Alternatively, if you don’t give a block to Database#transaction, the transaction remains open until you explicitly call Database#commit or Database#rollback.
db.transaction db.execute( "insert into table values ( 'a', 'b', 'c' )" ) db.commit
Note that SQLite does not allow nested transactions, so you’ll get errors if you try to open a new transaction while one is already active. Use Database#transaction_active? to determine whether a transaction is active or not.
发表评论
-
ruby知识点滴
2011-04-25 16:20 7211、加入文件所在路径 $: << (" ... -
ruby读取SQLite的图片数据并插入word中
2011-04-24 11:18 1133表的结构请参看 http://xineohpanihc ... -
ruby 将图片读入sqlite,再取出
2011-04-24 09:32 1574# -*- coding: utf-8 -*- req ... -
ruby 读写图片文件
2011-04-24 09:25 1523# -*- coding: utf-8 -*- f ... -
ruby textfile vs binaryfile
2011-04-23 22:05 970The Difference Between Binar ... -
Ruby操作Sqlite详解示例 --转
2011-04-23 21:31 2699A Quick Guide to SQLite an ... -
在windows下安装ruby1.9.2,rails3.0.3和DevKit--转
2011-04-23 15:54 1865在windows下安装ruby1.9.2,rails3 ... -
ruby操作word--输入文字和设置格式
2011-04-23 10:19 1722# coding: utf-8require "wi ... -
ruby操作sqlite
2011-04-23 10:14 879require 'sqlite3'db = SQLite3:: ... -
Ruby操作word时遇到中文问题
2011-04-22 17:56 754# coding: utf-8 require &qu ... -
打包ruby or rails成exe(英文)
2008-11-14 12:34 2250ruby2exe有两种选择: 1、使用rubyscript2e ... -
Ruby操作excel
2008-11-13 16:34 3698一、新建并打开excel文件 #newEmptyExcel.r ...
相关推荐
《SQLite3 Ruby绑定在Windows平台的应用与解析》 SQLite3是一种轻量级的、自包含的、无服务器的SQL数据库引擎,广泛应用于嵌入式系统和小型应用中。Ruby是面向对象的脚本语言,以其简洁优雅的语法和强大的功能深受...
下载source code中的sqlite-amalgamation-3410100.zip,与sqlite-autoconf-3410100.tar.gz, 2.解压 将下载的文件放到虚拟机中,解压 unzip sqlite-amalgamation-3410100.zip tar zxvf sqlite-autoconf-3410100....
python3.8在import sqlite3时报错误:ImportError: No module named '_sqlite3'。 将该文件解压后,放到python3.8目录下的lib-dynload目录下。 比如我的服务器路径:/usr/local/bin/python3/lib/python3.8/lib-...
《PyPI官网下载 | sqlite3-to-mysql-1.4.5.tar.gz——数据库迁移工具解析》 在Python的世界里,PyPI(Python Package Index)是开发者获取和分享开源软件包的重要平台。本文将深入探讨名为`sqlite3-to-mysql`的...
SQLiteStudio是一款功能强大的SQLite数据库管理工具,专为Windows操作系统设计。SQLite本身是一个开源、轻量级的嵌入式SQL数据库引擎,广泛应用于各种桌面应用程序、移动设备和服务器环境,尤其适合那些对数据库性能...
sqlite-netFx40-setup-bundle-x86-2010-1.0.113.0.exe
标题"sqlite-netFx46-setup-bundle SQlLite驱动下载"指的是SQLite针对.NET Framework 4.6的安装包。这个安装包包含了SQLite驱动程序,使得.NET开发者可以在他们的应用程序中无缝地集成SQLite数据库。这适用于那些...
sqlite-netFx40-setup-bundle-x64-2010-1.0.113.0
python3.8在import sqlite3时报错误:ImportError: No module named '_sqlite3'。
这个标题"sqlite-netFx451-setup-bundle-x86-2013"表明这是一款专为.NET Framework 4.5.1和Visual Studio 2013设计的SQLite集成包,适用于32位(x86)平台。"1.0.105.2"是该驱动程序的版本号,表示这是该驱动的某个...
sqlite-netFx46-setup-bundle-x64-2015-1.0.104.0
标题中的"sqlite-netFx451-static-binary-bundle-x64-2013-1.0.112.0.zip"表明这是一个针对.NET Framework 4.5.1、64位(x64)平台的SQLite静态二进制捆绑包,版本号为1.0.112.0。SQLite是一款开源的关系型数据库管理...
"sqlite-netFx40-setup-bundle-x86-2010-1.0.109.0" 是 SQLite 的一个特定版本,专为 .NET Framework 4.0 平台设计,并且是针对 32 位(x86)系统的安装包。 该安装包的版本号 "1.0.109.0" 表示这是 SQLite 客户端...
"sqlite-netFx451-setup-bundle-x86-2013-1.0.105.2.exe" 是一个针对VS2013的SQLite安装包,适用于x86架构的Windows系统,版本号为1.0.105.2。 1. **SQLite 介绍**: - SQLite是一个自包含、无服务器、零配置、...
支持sqlite 数据块加密解密插件。解压文件,将里面的SQLite.Interop.dll拷贝到SQLiteExpert的安装目录然后启动SQLiteExpert,Tools->Options->SQLite library,选择带SQLite.Interop.dll的项即可。
SQLite3 的简单封装,实现了最基本的增删查改, 里面有简单的数据库文件 data.s3db可供测试, /* // func name: open // param----begin----param // file : 文件名,包括路径 // param-----end-----param // ...
赠送jar包:sqlite-jdbc-3.34.0.jar; 赠送原API文档:sqlite-jdbc-3.34.0-javadoc.jar; 赠送源代码:sqlite-jdbc-3.34.0-sources.jar; 赠送Maven依赖信息文件:sqlite-jdbc-3.34.0.pom; 包含翻译后的API文档:...
标题中的"sqlite-netFx40-binary-Win32_2010-1.0.94.0.zip"指的是SQLite数据库的一个特定版本,适用于.NET Framework 4.0环境,面向Windows 32位操作系统,版本号为1.0.94.0。这个压缩包是为了解决在开发或运行过程...
sqlite3的驱动jar包,sqlite-jdbc-3.21.0.jar,支持sqlite3数据库
sqlite-netFx46-setup-bundle-x86-2015-1.0.109.0.exe 包含vs插件好使