our entire IT technical staff is all over RAILS and can''t seem to get
things done anymore, but we are sure having fun with RAILS. At any
rate, we have used RAILS to quickly synchronize our assets and give us
a "GOOGLY" interface to our $STUFF that we maintain. Helps out in a
huge hospital implementation when integration is as diffucult as
political.
I approached this with a "seperate" but "integrated"
approach without
doing my homework, and I need you for further advice (since this list
and #rubyonrails build most of it anyway).
situation:
5 rails Apps/DB''s:
IntelServers
MidrangeServers
Applications
ClinicalDevices
Executive View
The goal here was some of our db''s have things that were the same for
instance, network people uplink servers and ''server'' people
uplink
''switches'' and ''analysts'' support
''apps'' that run on ''servers''.
VERY quickly we had basic databases, (except the network guys who went
ballistic), all with similar interfaces individual logons and search
vacilities. BEAUTIFUL. However I wanted to AT LEAST be able to share
values within drop down menus on thins that were similar.
To make a long story even longer with one more question:
Would I benefit NOW by moving all these databases into one huge db and
reference them all as seperate tables, or will I be able to pull off a
before_filter in ApplicationAbstract to populate drop down menus
within our perspective _form.rhtml?
Basically I need this to happen across db''s:
<label
for="servers_UplinkDevice">Uplinkdevice</label><br/>
<%= select(''servers'', ''UplinkDevice'',
Uplinker.find_all.collect
{|uplinker| uplinker.device}) %>
Im assuming the short answer will be to move everybody into one big
happy db as suggested by the developers, however if the above is
entirely possible, for the purpose of momentum and "departmental"
control I would like to kick the idea around...
Thanks in advance... yet again.
