twowaysql 0.2.0

data/History.txt

@@ -0,0 +1,3 @@
+== 0.2.0 2008-09-03
+
+* Initial release

data/License.txt

@@ -0,0 +1,13 @@
+Copyright 2004-2008 the Seasar Foundation and the Others.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, 
+either express or implied. See the License for the specific language
+governing permissions and limitations under the License.

data/Manifest.txt

@@ -0,0 +1,38 @@
+History.txt
+License.txt
+Manifest.txt
+README.txt
+Rakefile
+config/hoe.rb
+config/requirements.rb
+issues/issue-25efcfc383f3b0f6c0e2730ae7c2975bb2b3de26.yaml
+issues/issue-39023ea09e17e2d64bcef03aa59cdfe38b78ad5b.yaml
+issues/issue-4bc308d55ae91f266e656162a4147d356de1166c.yaml
+issues/issue-897995fa10377eabdf597e8e7692f17087c76923.yaml
+issues/issue-bd38c1cdc965d73dd629a81db2de1bcdcf4b10b8.yaml
+issues/issue-f2b773020b54f839c03d899b38b5113c8fd991df.yaml
+issues/issue-f39b907d01d7fa93df8c7a9de2e1b5e27727ee0a.yaml
+issues/issue-f64d73ed4f9854f1ded77e6496dbf59cfb3770a7.yaml
+issues/project.yaml
+lib/twowaysql.rb
+lib/twowaysql/node.rb
+lib/twowaysql/parser.rb
+lib/twowaysql/parser.y
+lib/twowaysql/template.rb
+lib/twowaysql/version.rb
+script/console
+script/destroy
+script/generate
+script/txt2html
+setup.rb
+spec/large_sql_spec.rb
+spec/learning_regex_spec.rb
+spec/spec.opts
+spec/spec_helper.rb
+spec/twowaysql_spec.rb
+tasks/deployment.rake
+tasks/ditz.rake
+tasks/environment.rake
+tasks/racc.rake
+tasks/rspec.rake
+tasks/website.rake

data/README.txt

@@ -0,0 +1,382 @@
+= TwoWaySQL
+
+=== sites:
+* {Web Site}[http://twowaysql.rubyforge.org/]
+* {Project Page}[http://rubyforge.org/projects/twowaysql]
+* {API Doc}[http://twowaysql.rubyforge.org/rdoc/]
+* {Issue Tracking}[http://twowaysql.rubyforge.org/issues/]
+
+=== sources:
+* http://github.com/twada/twowaysql/tree/master
+
+
+
+== DESCRIPTION:
+
+
+=== What is TwoWaySQL
+
+'TwoWaySQL' is a concept, looks like a Template Engine for SQL.
+
+It is initially invented and implemented in Seasar project's S2Dao[http://s2dao.seasar.org/en/index.html].
+
+This package is a Ruby implementation of TwoWaySQL concept.
+
+
+=== Why TwoWaySQL
+
+Like any other technology, SQL is also in 80:20 world. 80% of SQL can be generated easily and automatically by O-R Mappers, 20% can not. 20% of your SQLs may large and complex, using CASE clause, self JOIN, UNION ALL, EXCEPT, ... these are the real strength of SQL and its set-based operations.
+
+We better use them, to get the most out of RDBMS power.
+
+TwoWaySQL encourages to write complex SQL manually. Just develop SQL using tools like pgAdmin3 in try and error style, then markup the SQL by TwoWaySQL. Usage and Features are in this doc.
+
+
+
+=== Advantage
+TwoWaySQL provides better separation of host language and SQL.
+
+With TwoWaySQL, you can
+* separate SQL (as file) from host language
+* bind variables to SQL using Substitution comments
+* modify SQL conditionally by using Directive comments
+* run and preview TwoWaySQL-style SQL by tools like pgAdmin3, since the SQL is still valid SQL.
+
+
+
+== One minute example
+
+  # given SQL string with TwoWaySQL comments
+  sql = <<-EOS
+    SELECT * FROM emp
+    /*BEGIN*/WHERE
+      /*IF ctx[:job]*/ job = /*ctx[:job]*/'CLERK' /*END*/
+      /*IF ctx[:deptno_list]*/ AND deptno IN /*ctx[:deptno_list]*/(20, 30) /*END*/
+      /*IF ctx[:age]*/ AND age > /*ctx[:age]*/30 /*END*/
+    /*END*/
+    /*IF ctx[:order_by] */ ORDER BY /*$ctx[:order_by]*/id /*$ctx[:order]*/ASC /*END*/
+  EOS
+
+
+  # parse the SQL to create template object
+  template = TwoWaySQL::Template.parse(sql)
+
+
+  # merge data with template
+  data = {
+    :age => 35,
+    :deptno_list => [10,20,30],
+    :order_by => 'age',
+    :order => 'DESC'
+  }
+  merged = template.merge(data)
+
+
+  expected_sql = <<-EOS
+    SELECT * FROM emp
+     WHERE
+      
+      deptno IN (?, ?, ?)
+      AND age > ?
+
+     ORDER BY age DESC
+  EOS
+
+  merged.sql == expected_sql      #=> true
+  merged.bound_variables          #=> [10,20,30,35]
+
+
+  # use merged SQL and variables with any O-R Mapper you like (ex. Sequel)
+  require 'sequel'
+  DB = Sequel.connect('postgres://user:pass@localhost:5432/mydb')
+  rows = DB.fetch(merged.sql, *merged.bound_variables).all
+  . . .
+
+
+==== What TwoWaySQL intended to do
+* TwoWaySQL is intended to be a small and simple module.
+* TwoWaySQL respects SQL and its set-based operations. TwoWaySQL assists writing complex SQL with ease.
+* TwoWaySQL is not a replacement of ActiveRecord,Sequel,or any other O-R Mappers. Instead, TwoWaySQL will work with O-R Mappers well as a SQL construction module.
+
+
+==== What TwoWaySQL is not
+TwoWaySQL is not
+* an O-R Mapper
+* a SQL Parser
+* a framework
+* a Prepared Statement
+
+
+
+== FEATURES/PROBLEMS:
+
+* Substitution comments
+  * Bind variable comment
+  * Embedded variable comment
+
+* Directive comments
+  * IF comment
+  * ELSE comment
+  * BEGIN comment
+
+* actual SQL comment
+
+
+=== Known limitations
+
+* currently, ruby version of TwoWaySQL cannot parse multi-line comments.
+
+
+
+== SYNOPSIS:
+
+NOTE: some of this section is based on docs for S2Dao[http://s2dao.seasar.org/en/s2dao.html#SQLBind]
+
+
+=== Published Classes
+
+TwoWaySQL::Template is the class you may only use. TwoWaySQL::Template acts as a Facade for this package, others are for internal use.
+
+
+=== Basic Usage
+
+==== Input
+* TwoWaySQL-style SQL(string,file or anything like IO) to TwoWaySQL::Template.parse to create template object (note: template object is stateless and reentrant, so you can cache it)
+  * (Optionally) TwoWaySQL::Template.parse accepts Hash of parse options as second argument
+* data object(Hash-like object) to the TwoWaySQL::Template#merge then TwoWaySQL will evaluate the data as 'ctx'.
+
+==== Output
+* SQL String with placeholders (generally, '?' is used for placeholders)
+* Array of bound variables for placeholders
+
+
+
+=== SQL comment
+
+Firstly, In TwoWaySQL, expressions are written within SQL comment such as within "/**/" and "--". SQL may still be executed since TwoWaySQL specific, non-SQL expressions are written within comments. As a best practice, it is better to first write and test SQL and then write expressions within comments.
+
+To write actual comments in SQL, *insert a space* after "/*" before the comment string. For example, /* hoge*/. TwoWaySQL will recognize the space(s) after the comment start ("/*") and treat the enclosed content as an actual comment.
+
+
+
+=== Bind variable comment
+
+Bind variable comment is used to bind value(s) to the SQL.
+Literal to the right of bind variable comment is automatically replaced with a value.
+Bind variable comment syntax is as follows:
+
+  /*variable_name*/Literal
+
+TwoWaySQL may use bind variable as follows. In this case, value of ctx[:empno] is automatically set. Data object that is passed to TwoWaySQL::Template#merge is evaled as name 'ctx'.
+
+  SELECT * FROM emp WHERE empno = /*ctx[:empno]*/7788
+
+===== usage
+
+  sql = "SELECT * FROM emp WHERE job = /*ctx[:job]*/'CLERK' AND deptno = /*ctx[:deptno]*/20"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+  merged = template.merge(:job => "HOGE", :deptno => 30)
+  merged.sql                #=> "SELECT * FROM emp WHERE job = ? AND deptno = ?"
+  merged.bound_variables    #=> ["HOGE", 30]
+
+
+
+==== IN clause
+
+To bind multiple values in an IN clause, you can also use bind variable comment as well.
+
+  IN /*argument name*/(...)
+
+TwoWaySQL may use bind variable as follows. In this case, ctx[:names] is automatically replaced with placeholders associated with number of values in the data.
+
+  IN /*ctx[:names]*/('aaa', 'bbb')
+
+acceptable argument for IN clause is an array-like object. Say, Object that respond_to 'to_ary'.
+
+===== usage
+
+  sql = "SELECT * FROM emp WHERE deptno IN /*ctx[:deptnoList]*/(10, 20) ORDER BY ename"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+  merged = template.merge(:deptnoList => [30,40,50])
+  merged.sql                #=> "SELECT * FROM emp WHERE deptno IN (?, ?, ?) ORDER BY ename"
+  merged.bound_variables    #=> [30,40,50]
+
+  merged2 = template.merge(:deptnoList => [80])
+  merged2.sql                #=> "SELECT * FROM emp WHERE deptno IN (?) ORDER BY ename"
+  merged2.bound_variables    #=> [80]
+
+
+==== LIKE
+
+If you want to use "LIKE", you may write bind variables:
+
+  ename LIKE /*ctx[:ename]*/'hoge'
+
+Unfortunately, there is no special support for "LIKE". So, to use a wildcard character, add wildcard directy to the data. For example, to specify to include "COT", add wildcard character in the value as follows:
+
+  :ename => "%COT%"
+
+
+
+==== Embedded variable comment
+
+You can use Embedded variable comment to embed value directly (say without quoting or escaping) into the SQL as a string. Literal to the right of the Embedded variable comment will be replaced with value. Embedded variable comment has the following syntax:
+
+  /*$variable name*/Literal
+
+===== CAUTION:
+As you noticed. Embedded variable comment has risk for SQL Injection. Please note, like any other 'eval' usage of TwoWaySQL, Embedded variable comment evals the data in safe level 4. Therefore, dangerous actions in Ruby world (ex. system call, valiable assignments, tainted strings) are never executed. However, this is not enough. Valid ruby string is still dangerous string as SQL fragments. Do NOT use user input or any other strings outside your code. If you use Embedded variable comment, you should carefully check the data and its origin.
+
+===== usage
+
+  sql = "SELECT * FROM emp ORDER BY /*$ctx[:order_by]*/ename /*$ctx[:order]*/ASC"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+  merged = template.merge(:order_by => 'id, :order => 'DESC')
+  merged.sql                #=> "SELECT * FROM emp ORDER BY id DESC"
+  merged.bound_variables    #=> []
+
+
+
+=== IF comment
+
+To change SQL during execution based on a condition, use IF comments. IF comment has the following syntax:
+
+  /*IF condition*/ .../*END*/
+
+An example of IF comment is as follows:
+
+  /*IF ctx[:foo]*/hoge = /*ctx[:hoge]*/'abc'/*END*/
+
+When the condition returns a truthy value, TwoWaySQL treats statements in "/*IF*/" and "/*END*/" as active. In the above example, "hoge = /*ctx[:hoge]*/'abc'" will be output only when 'eval(ctx[:foo])' retuens an truthy value.
+
+
+==== usage
+
+  sql = "SELECT * FROM emp/*IF ctx[:job] */ WHERE job = /*ctx[:job]*/'CLERK'/*END*/"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+
+  # active case
+  merged = template.merge(:job => 'MANAGER')
+  merged.sql                 #=> 'SELECT * FROM emp WHERE job = ?'
+  merged.bound_variables     #=> ['MANAGER']
+
+  # inactive case
+  ctx = {}
+  merged2 = template.merge(ctx)
+  merged2.sql                #=> 'SELECT * FROM emp'
+  merged2.bound_variables    #=> []
+
+
+
+=== ELSE comment
+
+You can use ELSE comment to activate statements when condition is false. Sn example of IF comment with ELSE is as follows.
+
+  /*IF ctx[:foo]*/hoge = /*ctx[:hoge]*/'abc'
+    -- ELSE hoge IS NULL
+  /*END*/
+
+In this case, when the eval(ctx[:foo]) returns an falsy value, string "hoge IS NULL" will be active.
+
+
+==== ELSE comment sample
+
+  sql = "SELECT * FROM emp WHERE /*IF ctx[:job]*/job = /*ctx[:job]*/'CLERK'-- ELSE job IS NULL/*END*/"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+  # active case
+  merged = template.merge(:job => 'MANAGER')
+  merged.sql                 #=> 'SELECT * FROM emp WHERE job = ?'
+  merged.bound_variables     #=> ['MANAGER']
+
+  # inactive case
+  ctx = {}
+  merged2 = template.merge(ctx)
+  merged2.sql                #=> 'SELECT * FROM emp WHERE job IS NULL'
+  merged2.bound_variables    #=> []
+
+
+
+
+=== BEGIN comment
+
+BEGIN comment is used to not output WHERE clause when all IF comment in a WHERE clause, which does not include an ELSE, is false. BEGIN comment should used with IF comment.
+
+BEGIN comment syntax is as follows:
+
+  /*BEGIN*/WHERE clause/*END*/
+
+So, BEGIN comment example is as follows:
+
+  /*BEGIN*/WHERE
+    /*IF ctx[:job]*/job = /*ctx[:job]*/'CLERK'/*END*/
+    /*IF ctx[:deptno]*/AND deptno = /*ctx[:deptno]*/20/*END*/
+  /*END*/
+
+In the above example, 
+* when job and deptno are nil, WHERE clause will not be outputted.
+* When ctx[:job] == nil and ctx[:deptno] != nil, then sql will "WHERE depno = ?".
+* When ctx[:job] != nil and ctx[:deptno] == nil, then sql will "WHERE job = ?".
+* When ctx[:job] != nil and ctx[:deptno] != nil, then sql will "WHERE job = ? AND depno = ?".
+
+
+==== usage
+
+  sql = "SELECT * FROM emp/*BEGIN*/ WHERE /*IF ctx[:job]*/job = /*ctx[:job]*/'CLERK'/*END*//*IF ctx[:deptno]*/ AND deptno = /*ctx[:deptno]*/20/*END*//*END*/"
+  template = TwoWaySQL::Template.parse(sql, :preserve_eol => false)
+
+  # when data is empty (no param exists)
+  ctx = {}
+  merged = template.merge(ctx)
+  merged.sql                 #=> 'SELECT * FROM emp'
+  merged.bound_variables     #=> []
+
+  # when :job param exists
+  merged2 = template.merge(:job => 'MANAGER')
+  merged2.sql                #=> 'SELECT * FROM emp WHERE job = ?'
+  merged2.bound_variables    #=> ['MANAGER']
+
+  # when :job and :deptno param exists
+  ctx3 = {}
+  ctx3[:job] = "MANAGER"
+  ctx3[:deptno] = 20
+  merged3 = template.merge(ctx3)
+  merged3.sql                #=> 'SELECT * FROM emp WHERE job = ? AND deptno = ?'
+  merged3.bound_variables    #=> ['MANAGER',20]
+
+
+
+== REQUIREMENTS:
+
+* racc/parser (basically bundled with ruby)
+
+
+== INSTALL:
+
+* sudo gem install twowaysql
+
+
+== AUTHOR:
+
+* Takuto Wada(takuto.wada at gmail dot com)
+
+
+== LICENSE:
+
+Copyright 2004-2008 the Seasar Foundation and the Others.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, 
+either express or implied. See the License for the specific language
+governing permissions and limitations under the License.

data/Rakefile

@@ -0,0 +1,4 @@
+require 'config/requirements'
+require 'config/hoe' # setup Hoe + all gem configuration
+
+Dir['tasks/**/*.rake'].each { |rake| load rake }

data/config/hoe.rb

@@ -0,0 +1,73 @@
+require 'twowaysql/version'
+
+AUTHOR = 'Takuto Wada'  # can also be an array of Authors
+EMAIL = "takuto.wada at gmail dot com"
+DESCRIPTION = "Template Engine for SQL"
+GEM_NAME = 'twowaysql' # what ppl will type to install your gem
+RUBYFORGE_PROJECT = 'twowaysql' # The unix name for your project
+HOMEPATH = "http://#{RUBYFORGE_PROJECT}.rubyforge.org"
+DOWNLOAD_PATH = "http://rubyforge.org/projects/#{RUBYFORGE_PROJECT}"
+EXTRA_DEPENDENCIES = [
+#  ['activesupport', '>= 1.3.1']
+]    # An array of rubygem dependencies [name, version]
+
+@config_file = "~/.rubyforge/user-config.yml"
+@config = nil
+RUBYFORGE_USERNAME = "twada"
+def rubyforge_username
+  unless @config
+    begin
+      @config = YAML.load(File.read(File.expand_path(@config_file)))
+    rescue
+      puts <<-EOS
+ERROR: No rubyforge config file found: #{@config_file}
+Run 'rubyforge setup' to prepare your env for access to Rubyforge
+ - See http://newgem.rubyforge.org/rubyforge.html for more details
+      EOS
+      exit
+    end
+  end
+  RUBYFORGE_USERNAME.replace @config["username"]
+end
+
+
+REV = nil
+# UNCOMMENT IF REQUIRED:
+# REV = YAML.load(`svn info`)['Revision']
+VERS = TwoWaySQL::VERSION::STRING + (REV ? ".#{REV}" : "")
+RDOC_OPTS = ['--quiet', '--title', 'twowaysql documentation',
+    "--opname", "index.html",
+    "--line-numbers",
+    "--main", "README",
+    "--inline-source"]
+
+class Hoe
+  def extra_deps
+    @extra_deps.reject! { |x| Array(x).first == 'hoe' }
+    @extra_deps
+  end
+end
+
+# Generate all the Rake tasks
+# Run 'rake -T' to see list of generated tasks (from gem root directory)
+$hoe = Hoe.new(GEM_NAME, VERS) do |p|
+  p.developer(AUTHOR, EMAIL)
+  p.description = DESCRIPTION
+  p.summary = DESCRIPTION
+  p.url = HOMEPATH
+  p.rubyforge_name = RUBYFORGE_PROJECT if RUBYFORGE_PROJECT
+  p.test_globs = ["test/**/test_*.rb"]
+  p.clean_globs |= ['**/.*.sw?', '*.gem', '.config', '**/.DS_Store']  #An array of file patterns to delete on clean.
+
+  # == Optional
+  p.changes = p.paragraphs_of("History.txt", 0..1).join("\n\n")
+  #p.extra_deps = EXTRA_DEPENDENCIES
+
+    #p.spec_extras = {}    # A hash of extra values to set in the gemspec.
+  end
+
+CHANGES = $hoe.paragraphs_of('History.txt', 0..1).join("\\n\\n")
+PATH    = (RUBYFORGE_PROJECT == GEM_NAME) ? RUBYFORGE_PROJECT : "#{RUBYFORGE_PROJECT}/#{GEM_NAME}"
+$hoe.remote_rdoc_dir = File.join(PATH.gsub(/^#{RUBYFORGE_PROJECT}\/?/,''), 'rdoc')
+$hoe.rsync_args = '-av --delete --ignore-errors'
+$hoe.spec.post_install_message = File.open(File.dirname(__FILE__) + "/../PostInstall.txt").read rescue ""

data/config/requirements.rb

@@ -0,0 +1,15 @@
+require 'fileutils'
+include FileUtils
+
+require 'rubygems'
+%w[rake hoe newgem rubigen].each do |req_gem|
+  begin
+    require req_gem
+  rescue LoadError
+    puts "This Rakefile requires the '#{req_gem}' RubyGem."
+    puts "Installation: gem install #{req_gem} -y"
+    exit
+  end
+end
+
+$:.unshift(File.join(File.dirname(__FILE__), %w[.. lib]))

data/issues/issue-25efcfc383f3b0f6c0e2730ae7c2975bb2b3de26.yaml

@@ -0,0 +1,18 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: better whitespace handling
+desc: better whitespace handling on Scanner/Grammer.
+type: :feature
+component: twowaysql
+release: 
+reporter: takuto <takuto.wada@gmail.com>
+status: :unstarted
+disposition: 
+creation_time: 2008-09-03 09:00:15.483485 Z
+references: []
+
+id: 25efcfc383f3b0f6c0e2730ae7c2975bb2b3de26
+log_events: 
+- - 2008-09-03 09:01:47.792705 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - fix some dirty rules for whitespaces, if possible.

data/issues/issue-39023ea09e17e2d64bcef03aa59cdfe38b78ad5b.yaml

@@ -0,0 +1,26 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: integrate ditz html into site
+desc: Integrate ditz html output into site. Ditz site(http://ditz.rubyforge.org/ditz) may help.
+type: :task
+component: twowaysql
+release: 
+reporter: takuto <takuto.wada@gmail.com>
+status: :closed
+disposition: :fixed
+creation_time: 2008-09-04 17:19:57.462508 Z
+references: []
+
+id: 39023ea09e17e2d64bcef03aa59cdfe38b78ad5b
+log_events: 
+- - 2008-09-04 17:20:02.538939 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - ""
+- - 2008-09-04 21:28:42.162604 Z
+  - takuto <takuto.wada@gmail.com>
+  - changed status from unstarted to in_progress
+  - integrate using rake
+- - 2008-09-04 22:00:49.377211 Z
+  - takuto <takuto.wada@gmail.com>
+  - closed with disposition fixed
+  - done.

data/issues/issue-4bc308d55ae91f266e656162a4147d356de1166c.yaml

@@ -0,0 +1,24 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: "'binding' object support"
+desc: TwoWaySQL::Template#merge should accept 'binding' object?
+type: :feature
+component: twowaysql
+release: 
+reporter: takuto <takuto.wada@gmail.com>
+status: :unstarted
+disposition: 
+creation_time: 2008-09-03 08:37:03.712475 Z
+references: []
+
+id: 4bc308d55ae91f266e656162a4147d356de1166c
+log_events: 
+- - 2008-09-03 08:41:40.758367 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - |-
+    pros:
+      - user can control names in TwoWaySQL comments
+      - works well with ActiveRecord?
+    cons:
+      - any security risk?
+      - increase coupling between host language and SQL

data/issues/issue-897995fa10377eabdf597e8e7692f17087c76923.yaml

@@ -0,0 +1,26 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: RubyForge settings
+desc: Releases and documents will be hosted on RubyForge
+type: :task
+component: twowaysql
+release: 0.2 release
+reporter: takuto <takuto.wada@gmail.com>
+status: :in_progress
+disposition: 
+creation_time: 2008-09-04 17:02:51.175082 Z
+references: []
+
+id: 897995fa10377eabdf597e8e7692f17087c76923
+log_events: 
+- - 2008-09-04 17:03:44.376333 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - |-
+    1. get user account
+    2. create twowaysql project
+    3. some settings for upload
+    4. any other task?
+- - 2008-09-04 21:20:14.555151 Z
+  - takuto <takuto.wada@gmail.com>
+  - changed status from unstarted to in_progress
+  - ""

data/issues/issue-bd38c1cdc965d73dd629a81db2de1bcdcf4b10b8.yaml

@@ -0,0 +1,26 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: rdoc for published classes and methods
+desc: rdoc for published classes and methods
+type: :task
+component: twowaysql
+release: 0.2 release
+reporter: takuto <takuto.wada@gmail.com>
+status: :closed
+disposition: :fixed
+creation_time: 2008-09-03 08:43:57.377882 Z
+references: []
+
+id: bd38c1cdc965d73dd629a81db2de1bcdcf4b10b8
+log_events: 
+- - 2008-09-03 08:44:14.224213 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - docs needed for published classes and methods
+- - 2008-09-05 05:54:35.728338 Z
+  - takuto <takuto.wada@gmail.com>
+  - changed status from unstarted to in_progress
+  - start
+- - 2008-09-05 07:35:16.577247 Z
+  - takuto <takuto.wada@gmail.com>
+  - closed with disposition fixed
+  - docs not completed for forwardable methods. better reorganized?

data/issues/issue-f2b773020b54f839c03d899b38b5113c8fd991df.yaml

@@ -0,0 +1,18 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: change line-based scanning to whole string based scanning
+desc: try whole string based scanning to handle multiline comments and directives
+type: :task
+component: twowaysql
+release: 
+reporter: takuto <takuto.wada@gmail.com>
+status: :unstarted
+disposition: 
+creation_time: 2008-09-03 09:04:04.695887 Z
+references: []
+
+id: f2b773020b54f839c03d899b38b5113c8fd991df
+log_events: 
+- - 2008-09-03 09:04:46.759048 Z
+  - takuto <takuto.wada@gmail.com>
+  - created
+  - this is a trial. not necessary for current specs.