Page 1 of 1

Query builder problems

Posted: Wed Nov 26, 2008 10:39 am
by Larusso
Hello.
My company gives designing functionality to end user. We came up with such issues:

1) Query builder shows all tables in the database. Can there be some metadatafilter properties for programmer to limit visibility of tables?
2) We have oracle database, so we use Your oracle provider with minor changes. We found out that in implemented databases are other syntaxproviders for query builder which give easy way to insert parameters in criteria column e.g.:
when i write "> :param" it stays like i wrote. In syntax for oracle i changes it to "= '> :param'". Can other syntax provider be used for oracle database, maybe some kind of universalsyntaxprovider?
3) Can "Select Type of Data" be ommited, instead programatically set? If we give end user possibility only to connect to current database, he doesn't need to know what kind of database it is, choosing between many unusable data types.
4) If parameter is date or datetime there is textbox to set its value. It is a problem, because in different localizations date is parsed differently. Can there be added calendar?
Regards

Query builder problems

Posted: Wed Nov 26, 2008 7:16 pm
by Edward
Hello Larusso.
Larusso wrote:My company gives designing functionality to end user. We came up with such issues:

1) Query builder shows all tables in the database. Can there be some metadatafilter properties for programmer to limit visibility of tables?
2) We have oracle database, so we use Your oracle provider with minor changes. We found out that in implemented databases are other syntaxproviders for query builder which give easy way to insert parameters in criteria column e.g.:
when i write "> :param" it stays like i wrote. In syntax for oracle i changes it to "= '> :param'". Can other syntax provider be used for oracle database, maybe some kind of universalsyntaxprovider?
3) Can "Select Type of Data" be ommited, instead programatically set? If we give end user possibility only to connect to current database, he doesn't need to know what kind of database it is, choosing between many unusable data types.
Sorry, we do not have plans to modify work of the Query Builder right now. The reasons I have described you in the letter I sent regarding this. Sorry, but there is no other way right now.
4) If parameter is date or datetime there is textbox to set its value. It is a problem, because in different localizations date is parsed differently. Can there be added calendar?
Yes, we have plans about modifications of work with parameters. Does the DateTimePicker component solve the problem with different ways of displaying of data?

Thank you.

Query builder problems

Posted: Thu Nov 27, 2008 11:16 am
by Larusso
datetimepicker uses localization so it should help

Query builder problems

Posted: Fri Nov 28, 2008 11:19 am
by Vital
Hello,
Larusso wrote:datetimepicker uses localization so it should help
You can use DatePickerFormat property of StiWebViewer. This property have value "yyyy/mm/dd" by default.

Thank you.