search for: _empty_

how do I create a data frame with the given column names _NOT KNOWN IN ADVANCE_? i.e., I have a vector of strings for names and I want to get an _EMPTY_ data frame with these column names. is it at all possible? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.3 (Final) http://openvotingconsortium.org http://pmw.org.il http://memri.org http://mideasttruth.com http://palestinefacts.org I don't like cats! -- Come on, you just don...

Nick, What are you planning on running over the shared connection? Database, eMail, File Shares? How many users? How much data? What is your I/O profile? I've worked with 'enterprise' storage most of my career either as a consumer, adviser or provider - can't comment on AoE other than to suggest you look at what are the business & technical goals, how they solve it and what

...do |t| t.column :JobReferenceNumber, :integer, :null => false t.column :warning_id, :integer, :null => false end What I find in both my app. and ruby script/console is the following: If I run the following three statements against a saved Job object j with JobReferenceNumber 550, and an _empty_ jobs_warnings table: j.warnings << Warning.find(3) j.warnings << Warning.find(2) j.warnings << Warning.find(1) I end up seeing rows in the jobs_warnings table with id: 3 JobReferenceNumber: 550 warning_id: 3 id: 2 JobReferenceNumber: 550 warning_id: 2 id: 1 JobReferenceNumber...

Hi all, Recently there''s been discussion [1] in the Linux community about how filesystems should deal with rename(2), particularly in the case of a crash. ext4 was found to truncate files after a crash, that had been written with open("foo.tmp"), write(), close() and then rename("foo.tmp", "foo"). This is because ext4 uses delayed allocation and may not