ip.pages relationship field

[Ali Majrashi]

this is one of the best field type in v3 i hope soon we will se it in IPS4 

can IPS team improve it to include more advance usage something like 

1. one -> one relationship
2. one -> many relationship
3. many -> many relationship

one -> one relationship

for example (just example) i got database for employee to fill their important information 

name,age,mobile,education level etc.

and got another database for CVs so each employee can submit only one CV

this can be long list of fields he need to fill

so when he start new record to fill his information he can fill both in the same form his information and his CV information

and one record link only to one cv based on the record ID also when he need to edit it he can edit both in the same form 

the same goes if he try to insert new CV he will be asked to link it to exiting record if any or create new one

you can also have third database for certificate and link it to his record this can be one -> many relationship so he can insert more than one certificate and link it to his information record

 

one -> many relationship

for example you got car database (i'm bad when it's come to cars)

you can create database for manufacture name or brand names

another database for cars and their basic information this can be one -> many relationship each brand can have many cars under it

also another database for each car model release with more info about each release like the year, model, pictures, colours etc.

 

many -> many relationship

is complex one but useful when you need a record to be linked to many other records and vice versa 

 

when we link database based on the record ID can we have more options and power on the edit/create form of what fields we need to edit or add to each database 

[NewRockRabbit]

Hopefully this will be put into the Feature Plan (when it returns).

[opentype]

this is one of the best field type in v3 i hope soon we will se it in IPS4 

Well it NEEDS to come back soon. I can hardly imagine that the official 4.0 announcement will have a big warning: “by the way, you can’t upgrade from 3.4 if you used that field. That will break your site.”

 

so when he start new record to fill his information he can fill both in the same form his information and his CV information

and one record link only to one cv based on the record ID also when he need to edit it he can edit both in the same form 

Wow, that sounds like a VERY special request. I can’t really imagine that as stock functionality. 

The other things (1:n, n:n) are already possible. Not sure what you are asking for there. 
For cars for example, the missing functionality isn’t the database connections, but the fields within one database which are based on another, i.e. “conditional fields” while adding a record. 

 

My number 1 feature request for the relational field is the ability to retrieve data from the linked field. 
For example: If I add a music album to the music album database and link the artist in the artist database and the record label in the record label database, then I don’t want to just see their names in the record view (as it is in 3.4). I would also like to be able to show a picture of the artist, the logo and website of the record label and so on. So all data that is stored in those foreign records should be directly available. 

 

[Ali Majrashi]

Hopefully this will be put into the Feature Plan (when it returns).

​hopfully sooner i can't upgrade my 2 site becuase i use it alot and got many database linked to each other 

[Ali Majrashi]

Well it NEEDS to come back soon. I can hardly imagine that the official 4.0 announcement will have a big warning: “by the way, you can’t upgrade from 3.4 if you used that field. That will break your site.”

Wow, that sounds like a VERY special request. I can’t really imagine that as stock functionality. 

The other things (1:n, n:n) are already possible. Not sure what you are asking for there. 
For cars for example, the missing functionality isn’t the database connections, but the fields within one database which are based on another, i.e. “conditional fields” while adding a record. 

 

My number 1 feature request for the relational field is the ability to retrieve data from the linked field. 
For example: If I add a music album to the music album database and link the artist in the artist database and the record label in the record label database, then I don’t want to just see their names in the record view (as it is in 3.4). I would also like to be able to show a picture of the artist, the logo and website of the record label and so on. So all data that is stored in those foreign records should be directly available. 

 

​the relationship field in v3 is simple way to generate fields based on database connections by fields value which i love 

the real magic happen when we can link database to each others and have more control 

imagine your self creating a database and would love to create poll for each record without real linking it's difficult to achieve (this just another example)

with this you can organize your data and have more control on them 

IPS4 even the old version already got this by default this how database really got build and organized 

members,groups,permissions 

category,posts,comments in any app

by doing this you can expand manage improve and control your data easily and it's efficient this way

My number 1 feature request for the relational field is the ability to retrieve data from the linked field. 
For example: If I add a music album to the music album database and link the artist in the artist database and the record label in the record label database, then I don’t want to just see their names in the record view (as it is in 3.4). I would also like to be able to show a picture of the artist, the logo and website of the record label and so on. So all data that is stored in those foreign records should be directly available. 

i would love to see this also

when we have a real connection between database this can be easily done