Guest User

Untitled

a guest
Jul 20th, 2018
128
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.67 KB | None | 0 0
  1.  
  2. ActiveRecord::Base.establish_connection(
  3. :adapter => "mysql",
  4. :user => "root",
  5. :password => "",
  6. :database => "arvest"
  7. )
  8.  
  9.  
  10. class Employee < ActiveRecord::Base
  11. end
  12.  
  13. class Dependents < ActiveRecord::Base
  14. end
  15.  
  16. class WellnessPolicies < ActiveRecord::Base
  17. end
  18.  
  19. class WellnessScreening < ActiveRecord::Base
  20. end
  21.  
  22. class NewBillingRecord < ActiveRecord::Base
  23. end
  24.  
  25. person = WellnessScreening.find_by_sql(<<-SQL
  26. SELECT br.account_name, br.account_id,
  27. if((participant_first_name = "Spouse"), if((d.dependent_first_name != ""),d.dependent_first_name,participant_first_name), participant_first_name) as participant_first_name,
  28. participant_last_name,
  29. if((participant_first_name = "Spouse"), d.dependent_dob, e.dob) AS dob,
  30. ws.insured_first, ws.insured_last, ws.insured_id AS "",
  31. e.address, e.city, e.state, e.zip, e.home_phone,
  32. p.policy_number, p.policy_type
  33. FROM wellness_screenings as ws
  34. LEFT JOIN employees as e ON e.`employee_id` = ws.employee_id
  35. LEFT JOIN dependents as d ON d.employee_ident = ws.employee_id and d.dependent_relationship = "S" and ws.participant_first_name = "Spouse"
  36. LEFT JOIN wellness_policies as p ON ws.employee_id = p.payor_number
  37. JOIN newBillingRecord as br)
  38.  
  39. puts "Employee Record"
  40.  
  41. person.each do |p|
  42. puts %{#{p.payor_number} - #{p.employee_id} - #{p.policy}}
  43. end
  44.  
  45.  
  46. policy = WellnessPolicies.find(:first)
  47. puts "Wellness Record"
  48. puts %{ #{policy.payor_number} #{policy.payor_name} #{policy.policy_number} #{policy.policy_type} }
  49.  
  50. screening = WellnessScreening.find(:first)
  51. puts "Screening Record"
  52. puts %{ #{screening.account_name} #{screening.account_id} #{screening.employee_id} }
Add Comment
Please, Sign In to add comment