search for: part_names

...39;t exist (or fail if they don''t exist in the case of PartName) and return relevant error information to the user? I know this is all wrong, but would love a few pointers on the right way to do it!! Thank you in advance... - Ian -----------------Schema ------------------ CREATE TABLE part_names ( id serial primary key, part_name character varying NOT NULL, group_id integer not null, description character varying, idx_part_name tsvector ); ALTER TABLE part_names ADD CONSTRAINT pn_group FOREIGN KEY (group_id) REFERENCES groups(id) DEFERRABLE INITIALLY DEFERRED; CREATE...

...39;t exist (or fail if they don''t exist in the case of PartName) and return relevant error information to the user? I know this is all wrong, but would love a few pointers on the right way to do it!! Thank you in advance... - Ian -----------------Schema ------------------ CREATE TABLE part_names ( id serial primary key, part_name character varying NOT NULL, group_id integer not null, description character varying, idx_part_name tsvector ); ALTER TABLE part_names ADD CONSTRAINT pn_group FOREIGN KEY (group_id) REFERENCES groups(id) DEFERRABLE INITIALLY DEFERRED; CREATE...

In my controller, I do this to instantiate and populate my Part, PartName and PartNumber objects. def edit @part = Part.find(params[:id], :include => [:part_name, :part_number]) end But in the view, this doesn''t refer to the right object. I somehow need to indicate that the part_name object is a child of the part object. <%= text_field_with_auto_complete :part_name,

Hi, I have a question today regarding how the various form elements in _form.rhtml are named. I understand that for a database table "persons" with a column headed by "name", then in _form.rhtml it will probably be like: <p><label for="person_name">Name><br/> <%= text_field ''person'', ''name''

I have a hacked together version of Radiant with the capability of allowing users to add comments. It''s somewhere between "demo" and "pre-alpha" quality at the moment. I''ll make the code available (as an svn diff against HEAD) in the next few days to anybody who''s interested. Here''s a brain dump of the things I ran into, and my

Rework disk library to work on a firmware independent way. Each specific implementation goes through subdirs like "bios/" and "efi/" respectively. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/include/syslinux/disk.h | 50 +++- com32/lib/Makefile | 2 + com32/lib/syslinux/disk.c | 583