similar to: YAML failing to de-serialize

I figured I''d post here before submitting a ticket, but I''m seeing some confusing stuff when dealing with YAML now. I was using it to freeze objects in my database, and so i had some data already around to mess with. I upgraded both Ruby (1.8.3 -> 1.8.4) and Rails ( -> 1.1RC1) and this junk started. I''ve outlined the problem in two pastes, which I''ll

Dear R-help Group Scenario 1: I have a text file running to 1000 of lines...that is like as follows: [922] "FieldName: Wk3PackSubMonth" [923] "FieldValue: Apr" [924] "FieldName: Wk3PackSubYear" [925] "FieldValue: 2017" [926] "FieldName: Wk3Code1" [927] "FieldValue: " [928] "FieldValue: K4" [929] "FieldName:

Hi Vijayan, one way going about it *could* be this: library(dplyr) library(tidyr) library(purrr) ex_dat <- c("FName: fname1", "Fval: Fval1.name1", "Fval: ", "FName: fname2", "Fval: Fval2.name2", "FName: fname3") data.frame(x = ex_dat) %>% separate(x, c("F1", "F2"), sep = ": ") %>% filter(F2

@Don your solution does not solve Vijayan's scenario 2. I used spread and gather for that. An alternative solution to insert mising Fval - picking up with Don's newtst - is newtst <- c("FName: fname1", "Fval: Fval1.name1", "FName: fname2", "Fval: Fval2.name2", "FName: fname3", "FName: fname4", "Fval: fval4.fname4")

Using Ulrik?s example data (and assuming I understand what is wanted), here is what I would do: ex.dat <- c("FName: fname1", "Fval: Fval1.name1", "Fval: ", "FName: fname2", "Fval: Fval2.name2", "FName: fname3") tst <- data.frame(x = ex.dat, stringsAsFactors=FALSE) sp <- strsplit(tst$x, ':', fixed=TRUE) chk <-

Just getting back into Rails, so apologies. Just a bit of advice please. I''m trying to rewrite the change control app that I wrote originally in VB/Oracle. It''s used heavily by our project and customer and seems a good project to rewrite in rails, if not for this customer then perhaps for another. Anyway, I have decided to go with MySQL this time and have the following

Hi In the controller I have the function def convert_sd_ticket_to_incident ServiceDeskTicket.close_ticket(sd_id,created_by_id,modified_by_id) Incident.convert_sd_ticket_to_incident(sd_id,created_by_id,modified_by_id) end Now in the ServiceDeskTicket model def self.close_ticket(sd_id,created_by,modified_by) begin ActiveRecord::Base.transaction do

On 01/15/2010 11:37 AM, Talin wrote: > Yes, that's closer to the frontend semantics: the variants of a > union type don't have any natural ordering, so list semantics could > cause problems. I agree. I probably shouldn't even comment, as I know so little about LLVM. But I've hand-written a couple kLOC of IR now and am starting to get a feel for the

Dustin Laurence wrote: > On 01/15/2010 11:37 AM, Talin wrote: > >> Yes, that's closer to the frontend semantics: the variants of a >> union type don't have any natural ordering, so list semantics could >> cause problems. > > I agree. I probably shouldn't even comment, as I know so little about > LLVM. But I've hand-written a couple

I''m running Typo, and after a comment is successfully posted, Typo runs this snippet of Javascript: new Effect.BlindDown($(''commentList'').lastChild); which throws the following error under Firefox 1.5rc1 (OSX) Error: element.style has no properties Source File: http://laughingmeme.org/javascripts/effects.js Line: 754 The problem being that lastChild() is returning

I''m trying to do an IN query, where I have an array of user objects imaginatively named ''users'': :conditions=>["user_id IN (?)", users.collect{|u| u.id }.join('','')] this ends up with: ... IN(''1,2,3'') ... Obviously I want this to be: ... IN(1,2,3) ... or even ... IN(''1'', ''2'',

Last week I started to sketch out what would be involved in building a calendar app in Rails. In the process I went looking for what Ruby has in the way of Date/Time libraries, and in particular TimeZone support. Was (pleasantly?) surprised to find that Rails seems to have Ruby''s best timezone support. But it looks like it has a very serious bug, it isn''t daylight saving

Hello, i try to validate with JS if a Formfield has been filled with data. Usually I use "onsubmit()" in the form. My Code is <%= start_form_tag :action => ''update'', :id => @person.id, "onsubmit"=>"return isDateSet(document.forms[0].elements[''fieldname''].value)"; %> The JS-function returns false if length of

I''m building rails 3 with legacy oracle 10g db. which it''s sequence is non rails convension. I have try this. class AdCourt < ActiveRecord::Base set_sequence_name ''COURT_SEQ'' end with rails console : AdCourt.sequence_name I have got "COURT_SEQ" which look ok. When AdCourt.create!(:caption => ''AAAA'', :code =>

I have an HTML form on the screen, that is connected to a database (standard Ruby way). I found that there are people that would rather not fill in this information, but would rather search Amazon for the info. Therefore, I added a link to the right of one of the fields that, when pressed, will search Amazon for what ever you typed into that field. So, how can I do that? At first I tried

Hmm. if you put it *after* the ldap userdb, it should not have prevented users from logging in. What happens if you do userdb { ? driver = passwd-file ? args = .... ? skip = notfound ? result_failure = continue-ok } Aki On 07.08.2018 12:58, Simeon Ott wrote: > Now the attributes are correctly read for the user test at onnet.ch > <mailto:test at onnet.ch>, but other users are not

On Fri, Jan 15, 2010 at 12:41 AM, Joachim Durchholz <jo at durchholz.org>wrote: > Talin schrieb: > > Well, the fact that union members have to be indexed by number means that >> the ordering has to be part of the type - so even though type-theoretically >> union { i32, float } is the same as union { float, i32 }, in my >> implementation they are distinct types.

Talin schrieb: > Well, the fact that union members have to be indexed by number means > that the ordering has to be part of the type - so even though > type-theoretically union { i32, float } is the same as union { float, > i32 }, in my implementation they are distinct types. However, from the > standpoint of a frontend, this is not a great concern, because the > frontend

Hello, I''ve got a problem with deserialization of AR "serialize" method (http://apidock.com/rails/ActiveRecord/Base/serialize/class) in my tests. It just gives me pure String instead of my data Array. Example: User > AR::Base serialize :roles, Array end Console: u = User.new u.roles = ["admin", "support"] u.save # => true User.first.roles # =>

I''m just getting into RoR, coming from a long PHP background. So far I LOVE IT! I''m hitting a roadblock with updating my mysql database. For simplicities sake, I have 2 tables and here are the relevant columns. Table Users id name email Table Issues id createdby assignedto reportedby In my models I have everything mapped properly I believe. When I try to update the