/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */ /* * This file is part of the LibreOffice project. * * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. * * This file incorporates work covered by the following license notice: * * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. See the NOTICE file distributed * with this work for additional information regarding copyright * ownership. The ASF licenses this file to you under the Apache * License, Version 2.0 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.apache.org/licenses/LICENSE-2.0 . */ #ifndef __com_sun_star_form_component_DatabaseListBox_idl__ #define __com_sun_star_form_component_DatabaseListBox_idl__ #include #include #include module com { module sun { module star { module form { module component { /** This service specifies a data-aware list box control model.

The base service for list boxes (ListBox) offers only one possibility to specify the list entries: The display strings in the com::sun::star::awt::UnoControlListBoxModel::StringItemList property and the corresponding values in the ListBox::ListSource property.

This service here extends this mimic. It allows to fill the list from a data source. This means that a second result set is opened, which works on the same connection as the form which the list box belongs to, but can be based on an arbitrary table or SQL statement.

For instance, you may have a form which is bound to a table invoice, and you use it to enter invoices for your customers. Probably, you will have a second table (say customer), which (among other data) contains a unique key for identifying customers. In your invoice table, you will have a foreign key referring to these customers.
Now, besides the result set the form is based on (all your invoices), the list box can be instructed to open a second result set, this time for the customer table, and fill its list with entries from this result set.
Additionally, it allows to model the relation between the two tables: When the user selects a customer from the list, this customer has the unique id we just talked about (which is not necessarily visible to the user in any way). The list box then automatically transfers this id into the foreign key column of invoice, thus allowing the user to transparently work with human-readable strings instead of pure numbers.
Let's call this result set the list is filled from the list result set here ...

The display strings are always taken from the first column of that result set, and the corresponding value as per the BoundColumn property.

*/ published service DatabaseListBox { service com::sun::star::form::component::ListBox; service com::sun::star::form::DataAwareControlModel; /** specifies which column of the list result set should be used for data exchange.

When you make a selection from a list box, the "BoundColumn" property reflects which column value of a result set should be used as the value of the component. If the control is bound to a database field, the column value is stored in the database field identified by the property com::sun::star::form::DataAwareControlModel::DataField.

-1
The index (starting at 0) of the selected list box entry is stored in the current database field.
0 or greater
The column value of the result set at the position (0-indexed) is stored in the current database field. In particular, for value 0, the selected (displayed) list box string is stored.

The bound column property is only used if a list source is defined and the list source matches with the types com::sun::star::form::ListSourceType::TABLE, com::sun::star::form::ListSourceType::QUERY, com::sun::star::form::ListSourceType::SQL or com::sun::star::form::ListSourceType::SQLPASSTHROUGH. Otherwise the property is ignored, as there is no result set from which to get the column values.

*/ [property] short BoundColumn; /** describes the kind of list source used.

Depending on the value of this property, the way the value of ListBox::ListSource is evaluated varies.

com::sun::star::form::ListSourceType::VALUELIST
The elements in the string sequence in ListBox::ListSource build up the entry list.
com::sun::star::form::ListSourceType::TABLE
The first element of the string sequence in ListBox::ListSource determines the table which the list result set should be based on.
com::sun::star::form::ListSourceType::QUERY
The first element of the string sequence in ListBox::ListSource determines the query which the list result set should be based on.
For retrieving the query, the connection which the data form is working with (com::sun::star::sdb::RowSet::ActiveConnection) is queried for the com::sun::star::sdb::XQueriesSupplier interface.
com::sun::star::form::ListSourceType::SQL
The first element of the string sequence in ListBox::ListSource contains the SQL statement which the list result set should be based on.

com::sun::star::form::ListSourceType::SQLPASSTHROUGH
The first element of the string sequence in ListBox::ListSource contains the SQL statement which the list result set should be based on.
The statement is not analyzed by the parser. This means that you can use database specific SQL features here, but, on the other hand, lose features like parameter value substitution.
com::sun::star::form::ListSourceType::TABLEFIELDS
The first element of the string sequence in ListBox::ListSource determines the table whose column names should fill the list.

*/ [property] com::sun::star::form::ListSourceType ListSourceType; /** The selected values. */ [property, transient, optional] sequence< any > SelectedValues; /** The selected value, if there is at most one. */ [property, transient, optional] any SelectedValue; }; }; }; }; }; }; #endif /* vim:set shiftwidth=4 softtabstop=4 expandtab: */