composite

How to include a function that returns a composite type in a SELECT ? I have composite type: CREATE TYPE public.dm_nameid AS ( id public.dm_int, name public.dm_str ); Also, I have a function that returns this type fn_GetLinkedProject(integer) . And I need to make something like this: SELECT p.id, p.data, p.name, pl.id linked_id, pl.name linked_name FROM tb_projects p left join "fn_GetLinkedProject"(p.id) pl How can I do this? I have read this article. I don't want following method: SELECT p.id, p.data, p.name, (select pl1.id from "fn_GetLinkedProject"(p.id) pl1 ) linked_id, (select pl2.name

I am working with SWT and I would like to be able to resize a composite by dragging the corner of it, the same way that you can resize a shell. I'm sure someone out there has implemented a good solution. Thanks. I think what you are looking for can be implemented with org.eclipse.swt.widgets.Tracker here is sample working code: public static void main(String[] args) { Display display = new Display(); final Shell shell = new Shell(display); shell.open(); final Composite b = new Composite(shell, SWT.NONE); b.setBounds(20, 20, 80, 80); b.setBackground(display.getSystemColor(SWT.COLOR_BLUE)); b

I got this hibernate mapping: <class name="CoverageTerm" table="coverage_term"> <composite-id name="id" class="CoverageTermPK"> <key-many-to-one name="productTerm" class="ProductTerm"> <column name="termtype_id"></column> <column name="product_id" ></column> </key-many-to-one> <key-many-to-one name="productCoverage" class="ProductCoverage" column="product_coverage_id"></key-many-to-one> </composite-id> <property name="data"/> </class> This is a simple composite key mapping with a relation to table productCoverage and a composite key relation to productterm. Now the problem comes in my search

Per an answer to a previous question (answer here: SQL/Database Views in Grails ), I have tried to use a domain class to represent a view in my database. This works wonderfully in most cases, however: I have a view with no single unique key. Let's say the underlying tables look like this: A: id,varX 1,"Blah" 2,"Foo" 3,"Bar" B: id,A.id,C.id 1,2,1 2,2,2 3,3,1 C: id,varY 1,"Boom" 2,"Fizzle" My view looks like this: A.id,varX,B.id,C.id,varY 1,"Blah",NULL,NULL,NULL 2,"Foo",1,1,"Boom" 2,"Foo",2,2,"Fizzle" 3,"Bar",3,1,"Boom" That is exactly how it ought to look for our purposes. However, as you can

I have a question about this query: SELECT * FROM runs WHERE (NOW() BETWEEN began_at AND finished_at) Do you think it makes sense to create composite index for began_at and finished_at columns? Or it makes sense to create index only for began_at? Your style is very uncommon. Most people would probably write WHERE began_at < NOW() AND finished_at > NOW() However. I would recommend putting an index on both fields. A combined key wont be of use to you because you it would only speed up searcher for specific date combinations. Well this is not entirely true because if you use betree a combined key

Let's imagine I have a collection of nodes that I use for my Renderer class later on. Then I have a Visitor class that can visit node or whole collection. It's simple because my collection of nodes it's simply a wrapper to the std::list with few extra methods. The problem is I'd like to have a tree like structure for nodes(instead of simple list) so a node can have a parent and n children. That would be handy as I'd like to be able to pass to my Renderer a node and render everything "below" that node. The answer probably is Composite. How can I use together Visitor and Composite? I've read