search for: some_t

...le, instead, using R objects to represent elements of a database system (statements, clauses, operators, functions, fields, tables, etc.). R5 classes have made the development of this package somewhat easier than it would have been in the past (in my view, at least). Then an expression like: query(some_table$some_field)$where(some_table$some_field != NA & some_table$some_other_field %in% c(1, 2, 3)) would generate SQL like: SELECT `database`.`some_table`.`some_field` AS `some_field` WHERE `database`.`some_table`.`some_field` IS NOT NULL AND `database`.`some_table`.`some_other_field` IN (1, 2, 3...

...''s kind of annoying because I want the column to update every time the row gets changed. Is this a bug, or is there something I can do about it? (Obviously I can manually change my mysql table, but that kind of defeats the point of migrations!) In my migration file: create_table :some_table do |table| ... table.column :alter_date, :timestamp table.column :create_date, :datetime end But in mysql I get: CREATE TABLE `some_table` ( ... `alter_date` datetime default NULL, `create_date` datetime default NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB...

1) installation is not as smooth as some other plug-ins. If you follow the instructions on http://www.kanthak.net/opensource/file_column/ it makes a directory called trunk instead of file_column. You have to manually rename it to file_column. I guess this is a minor annoyance but it gives me the feeling that things aren''t quite like other plugins. 2) I get this error: undefined

...running on OSX 10.4.6 & Ruby 1.8.4 from darwinports. Any ideas how to get this working? BTW, the bug in AR is in the #add_column/#drop_column methods. Currently it isn''t handling reserved words correctly if one is used as a column name. Example Migration: self.up drop_column :some_table, :condition end MySQL allows the use of reserved words as column names provided they are quoted using the backtick. This is actually handled properly elsewhere in AR via the #quote_column_name method (in mysql_adapter.rb), but this method isn''t used in #add_column or #drop_col...

dose Ruby or ActiveRecord have the Java/JDBC equivalent for retrieving ResultSet meta data... PreparedStatement statement = null; try { statement = connection.prepareStatement("select * from some_table"); ResultSet rs = null; try { rs = statement.executeQuery(); ResultSetMetaData rsMetaData = rs.getMetaData(); int columnCount = rsMetaData.getColumnCount(); more stuff... -- Posted via http://www.ruby-forum.com/.

Hello everyone, I was wondering how i should do destination routing. I now do # ip rule add to x.x.x.x table some_table for each address i need. I was thinking about fwmark option. The problem is that routing decision is made after PREROUTING and not POSTROUTING (name obviously sais that :)) and i need to use -o. In OUTPUT this marking can''t be done. I made this conclusion by studying this URL: http:/...

Hi all, I''ve got an issue where i have a search page that passes a field which is then used as the criteria of the search. Problem is, I''ve set an AR has_many relationship in the model that joins one table to another - both tables have the same column name I''m searching on, so naturally I get an ambiguous error in sql - it doesnt know which column to apply the search

Dear all great developers. I wonder if there is any work being done or thoughts being shared regarding prepared SQL statements. Currently I am in heavy need of tuning SQL INSERTS that insert large (3MB) images into blobs. I am using rails 2.3.5 with postgres adapter and pg driver. Any information would be appreciated. Jarl -- You received this message because you are subscribed to the