Jruby 1.1.7 still leaking weakreferences
Key: JRUBY-3238
URL: http://jira.codehaus.org/browse/JRUBY-3238
Project: JRuby
Issue Type: Bug
Components: Java Integration
Affects Versions: JRu
I'm using Rails 2.2.2 and I started getting session errors when I
upgraded to JRuby 1.1.5. Message and call stack is below. I added some
debugging code to pstore.rb just to test my sanity (which is on shaky
grounds to begin with):
begin
content = Marshal::dump(table)
Marshal::loa
Clint Hill wrote:
I have no strong reason for defaulting to 255 other than the model in
question has around 20 attributes that are strings (name, agency,
policy, etc) and I didn't feel adding the ":limit => 255" to the
migration for each and every column was a good idea. I don't have to
for My
I have no strong reason for defaulting to 255 other than the model in
question has around 20 attributes that are strings (name, agency,
policy, etc) and I didn't feel adding the ":limit => 255" to the
migration for each and every column was a good idea. I don't have to
for MySQL, SQLite etc
Clint Hill wrote:
If I choose to limit the size to 255 as a default - is the proper
place to do that in the modify_types method call like so?
def modify_types(tp)
tp[:primary_key] = "NUMBER(38) NOT NULL PRIMARY KEY"
tp[:integer] = { :name => "NUMBER", :limit => 38 }
tp[:dat
If I choose to limit the size to 255 as a default - is the proper
place to do that in the modify_types method call like so?
def modify_types(tp)
tp[:primary_key] = "NUMBER(38) NOT NULL PRIMARY KEY"
tp[:integer] = { :name => "NUMBER", :limit => 38 }
tp[:datetime] = { :name =
IO.popen dosn't support forward slashes in Windows (diffrent behaviour to MRI)
--
Key: JRUBY-3237
URL: http://jira.codehaus.org/browse/JRUBY-3237
Project: JRuby
Issu
IO.popen dosn'
--
Key: JRUBY-3236
URL: http://jira.codehaus.org/browse/JRUBY-3236
Project: JRuby
Issue Type: Bug
Affects Versions: JRuby 1.1.6
Reporter: Mikael Rudberg
Assignee: Thomas E Enebo
--
