search for: middlenam

People, I want to design a historical sports db for my old school. I think at the moment it should be like: A year has many teams A team has many students A student has one lastname, firstname and middlename but a student can also have many teams (eg summer/winter abd over a number of years) . . Is there a problem with this? Doesn''t it just mean that there will be a student table with: id lastname firstname middlename and a separate "studentteams" table with: id student_id tea...

...a RODBC. For example, the user would type: retrieve firstName('JOHN') middlleName('WILLIAMS') lastName('FORD') This would generate the following SQL which would then be processed by RODBC: Select * from people where firstName = 'JOHN' and middleName = 'WILLIAMS' and lastName = 'FORD' Does anyone have a recommendation? Any ideas would be greatly appreciated. Alex

I am trying to get more out of auto_complete than it apparently was designed to deliver. My problems seem to be two fold. 1 - I use aggregations on names... :first_name, :middle_initial, :last_name and then aggregate them using a composed_of :wholename thing auto_complete_for seems to be wired to only use table columns directly and gags on the aggregate form. 2 - foreign table columns -

...I dont think it should do that. This causes problems further down the line when trying to access the Person object. Development Log file : "SQL (0.016000) select people_seq.nextval id from dual Person Create (0.015000) INSERT INTO people (title, weight, mothers_maiden_name, shoe_size, middlename, person_type, username, firstname, height, person_id, createdby, expired, name_string, surname) VALUES(''Mr'', ''100'', '''', 10, ''T'', null, null, ''T'', '''', :id, ''Chris Richards'...