Displaying 5 results from an estimated 5 matches for "hipertrack".
Did you mean:
hipertrac
2011 Jun 09
1
Rails 3.1 RC4 has broken migrations
...========================================
-- create_table(:users)
-> 0.0950s
-> 0 rows
== CreateUsers: migrated (0.0960s)
===========================================
rake aborted!
An error has occurred, this and all later migrations canceled:
wrong number of arguments (3 for 2)
/Users/hipertracker/.rvm/gems/jruby-1.6.2@rails-pre/gems/activerecord-
jdbc-adapter-1.1.1/lib/arjdbc/jdbc/adapter.rb:275:in `select''
/Users/hipertracker/.rvm/gems/jruby-1.6.2@rails-pre/gems/
activerecord-3.1.0.rc4/lib/active_record/connection_adapters/abstract/
database_statements.rb:9:in `select_all'...
2006 Jun 28
3
observe_field and radio button... does not work?
I try to catch click event on radio button, but nothing is executed....
Tested with RoR 1.1.2 and 1.1.3. What am I doing wrong?
<%= radio_button_tag(:city, ''Dublin'') %>
<%= observe_field(:citi, :frequency => 0.5,
:on => ''click'',
:with => "''city='' +
2005 Jul 24
0
[Active Record] Missing optional client encoding for MySQL 4.1
MySQL since version 4.1 can use utf-8 for multilangual tables, and it
uses almost the same approach like PosgreSQL where Active Record API
writes: ":encoding — An optional client encoding that is using in a
SET client_encoding TO <encoding> call on connection."
However ActiveRecord API does not mention how to set up optional
client encoding for MySQL 4.1...
2005 Jul 25
0
sqlsever, scaffold and set_primary_key
I found what was wrong with sqlserver adapter. I can rename "id" to
other name and it works. Only scaffold does not work correctly. It
ignores my set_primary_key command and is looking for "id" name.
--
JZ
2005 Jul 25
0
missing :encoding for mysql 4.1...
Because of missing :encoding parameter for mysql 4.1 I have to execute
the following command before any fetching queries:
ActiveRecord::Base.connection.execute("SET CHARACTER SET utf8")
and then I can use
@rows = MyModel.find(:all)
Without first query table returns ugly characters. It solved my
problem but it looks ugly. Definitely for MySQL 4.1. Rails needs
"encoding"