[Valentina-studio] Non-SQL record browser

[Klamp, Kurt]

> > 
> > why not? second pane popup shows the possible linked tables to the
> tables
> > used in first pane( 1.pane must always get recids of used tables). User
> > decides to see addtional data in linked table by choosing it in popup.
> > General: the routine in 2.pane looks for possible linked tables and if
> its
> > possible to show them it offers it in the popup
> 
> But JOIN TABLE, is not equal to original tables.
> This is NEW table. It is NOT linked to others table, and it have NO such
> info.
> 
Sorry Ruslan, but i don't understand it yet.

Assume there are 3 tables
Table 1: Person
	-Name 
	-Age
Table 2: Results
	-date
	-points
	-objptr to person
Table 3: Adress
	-street
	-city
	-zip
	-opjptr to person

and now i do a query in first pane like 'select * from person, results where
points>50
Why not see in second pane the linked data to first pane record like
'select * from adress where person.recid=objptr_to_person' without entering
this sql string, because for each record in first pane there can be
found/linked data in table 3 ?

Even if there is a aggregate function like

select name, (count date), sum(points), avg(points) from person, results
group by name

there is the same possible relation of each record in the resultset to table
3.

At least i think so.


> >> or result of GROUP BY...
> >> 
> > yes, or?
> 
> NO
> 
> > if i do a query with aggregate function in 2 tables and result which is
> > grouped by recid of one table, why not show in 2.pane additional data of
> > 3.table which is linked to grouped data table.
> 
> I think THIS and ABOVE what you say with JOIN, will be able to do with
> what
> I have name "creation RDB link on the fly".
> 
This can be additional, but if there are definite objptr relations we should
take them atomaticaly.



> >>> Jochen, I think this really can work...
> >>> Just later we will need more abstractions for this level.
> >>> 
> >>> Deal is that I want support in this way, NOT just ObjectPtrs, but ANY
> >> kind
> >>> of link between 2 tables:
> >>> 
> >>> 1) ObjectPTr
> >>> 
> >>> 2) RDB Link 
> >>>     a) default FOREIGN KEY in SQL and RDBMS
> >>>     b) LINK condition assigned by user on fly.
> >>>           Just only. To see something.
> >>> 
> >>> 3) New kind of link that can be M : M.
> >> 
> > That would be great. In first pane i've table 1, in second pane table 3
> and
> > link table 2 isn't visible and records in linktable 2 were created
> > automaticaly by Vstudio.
> 
> Right. This also can work.
> 
> But In fact I did mean new LINK feature, that will NOT require from you
> even
> creation of this third table that do MM link
> 
Even much better!!


Best,
Kurt