Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Latest commit

History

14 Commits

Folders and files

NameName
Last commit message
Last commit date

Repository files navigation

=SQL Anywhere DBD Driver for Ruby-DBI
This is a SQL Anywhere driver for Ruby DBI (http://ruby-dbi.rubyforge.org/). This driver requires the
native SQL Anywhere Ruby driver. To get the native driver, use:
gem install sqlanywhere
This driver is designed for use with DBI 0.4 and greater.
This driver is licensed under the Apache License, Version 2.
The official code repository is located on GitHub. The repository can be cloned with:
git clone git://github.com/sqlanywhere/dbd-sqlanywhere.git
==Making a Connection
The following code is a sample database configuration object that connects
to a database called 'Test'.
require 'dbi'
DBI.connect('DBI:SQLAnywhere:Test') do | dbh |
if dbh.ping
print "Successfully Connected"
end
end
The connection function takes the general form:
dbh = DBI.connect(DBNAME, [USER_NAME], [PASSWORD])
The DBNAME string can be specified in the following forms:
"DBI:SQLAnywhere:"
"DBI:SQLAnywhere:{ENG}"
"DBI:SQLAnywhere:{ENG}:{DBN}"
"DBI:SQLAnywhere:{CONNECTION_STRING}" # where CONNECTION_STRING ~= "key1=val1;key2=val2;..."
For the first form, nothing will be added to the connection string. With the second and third forms
the driver will add ENG and DBN to the connection string accordingly. The fourth form will pass
the supplied connection string through unmolested.
The USER_NAME and PASSWORD can be passed into the function and they will be automatically appended to the
connection string. Since Ruby DBI will automatically fill in the username and password with defaults if they are omitted, you should NEVER include a "UID=" or "PWD=" in your connection string or an exception will be thrown.
Examples: Function Call ==> Generated Connection String
==============================================================================================
DBI.connect("DBI:SQLAnywhere:") ==> "uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo") ==> "eng=Demo;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:Demo:Test", 'john', 'doe') ==> "eng=Demo;dbn=Test;uid=john;pwd=doe"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test") ==> "eng=Demo;dbn=Test;uid=dba;pwd=sql"
DBI.connect("DBI:SQLAnywhere:eng=Demo;dbn=Test;uid=john") ==> EXCEPTION! UID cannot be specified in the connection string
DBI.connect("DBI:SQLAnywhere:CommLinks=tcpip(port=2638)") ==> "CommLinks=tcpip(port=2638);uid=dba;pwd=sql"
==Running Test Suite
For information on running the Ruby/DBI DBD Tests, please see
test/DBD_TESTS
==Driver-Specific Features
At the time of this writing, there was no standard way to handle INOUT and OUT parameters
from stored procedures in DBI. When binding to an OUT parameter, you must bind a hash that contains a key called
:name. This :name will be used to retrieve the OUT value after execution. If the
OUT column is of string or binary type, you must also pass a key called :length with the expected maximum length of the OUT parameter.
In the case of an INOUT parameter, the :name and :length keys are the same as for
OUT parameters, but an additional :value parameter holds the value to be passed
into the stored procedure.
After execution, you can use the statement-specific function :bound_param
to retrieve the output value using the :name supplied at binding time.
===Example of using OUT and INOUT parameters
# The result that should be printed to console is:
# Complete string is PREFIX-some_string-SUFFIX and is 25 chars long
# Complete string is PREFIXPREFIX-some_string-SUFFIXSUFFIX and is 37 chars long
require 'dbi'
begin
DBI.connect("DBI:SQLAnywhere:test") do |dbh|
sql = <<SQL
IF EXISTS(SELECT * FROM SYS.SYSPROCEDURE where proc_name = 'foo') THEN
DROP PROCEDURE foo;
END IF
SQL
dbh.do(sql);
sql = <<SQL
create procedure foo ( IN prefix char(10),
INOUT buffer varchar(256),
OUT str_len int,
IN suffix char(10) )
begin set buffer = prefix || buffer || suffix;
select length( buffer ) into str_len; end SQL
dbh.do(sql);
buffer = "-some_string-"
prefix = "PREFIX"
# preparing the statement
sth = dbh.prepare("call foo( ?, ?, ?, ? )")
# Binding buffer column as :buf, and str_len column as :len
# Note that we must supply a :value for :buf since it is an INOUT
# And we must supply a :length for :buf since it is a string column
sth.execute( prefix, {:name => :buf, :value => buffer, :length => 255}, {:name => :len}, "SUFFIX")
# Retrieve the OUT value from buffer
new_buffer = sth.func(:bound_param, :buf)
# Retrieve the OUT value from str_len
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
# Add the results back into the string, and re-execute
sth.execute("PREFIX", {:name => :buf, :value => new_buffer, :length => 255}, {:name => :len}, "SUFFIX")
new_buffer = sth.func(:bound_param, :buf)
length = sth.func(:bound_param, :len)
puts "Complete string is #{new_buffer} and is #{length} chars long"
end
rescue DBI::DatabaseError => e
puts "An error occurred"
puts "Error code: #{e.err}"
puts "Error message: #{e.errstr}"
puts "Error SQLSTATE: #{e.state}"
ensure
DBI.disconnect_all
end

About

A driver that allows Ruby/DBI to communicate with SQL Anywhere

Resources

Stars

4 stars

Watchers

3 watching

Forks

Releases

Packages

Contributors

Languages