Automatically fill DefaultExpression when creating fields
Automatically fill DefaultExpression when creating fields
Hello,
is it possible to fill the DefaultExpression property of persistent fields, when adding them with the designer or creating a field at runtime?
I can do this partially at runtime using user_tab_columns, but integrating such a feature in odac would be a great enhancement!
Or is this already possible and I did not not find this functionality yet?
is it possible to fill the DefaultExpression property of persistent fields, when adding them with the designer or creating a field at runtime?
I can do this partially at runtime using user_tab_columns, but integrating such a feature in odac would be a great enhancement!
Or is this already possible and I did not not find this functionality yet?
Hello bork,
I did set Options.DefaultValues and created persistent fields afterwards. Is DefaultExpression property filled at runtime? I do not see any value in the object inspector.bork wrote:Hello
You should set the Options.DefaultValues option of your dataset to True and the DefaultExpression property of persistent fields will be filled automatically.
Hi bork,
DACVersion = '6.90.0.60';
OdacVersion = '6.90.0.56';
Using "About ODAC" yields "6.90.0.56 for RAD Studio 2009"
Using "About Unidac" yields "3.00.0.7 for RAD Studio 2009"
BTW: Is it possible to provide functions in Ora.pas, that return the OdacVersion and DacVersion, instead of using constants? When using packages, the "reported" version will differ from actual version since the compiler will "resolve" the constant at compile time!
running a compiled program yields:bork wrote:Hello
Please provide us the exact ODAC version that you are using (for example 6.90.0.59).
DACVersion = '6.90.0.60';
OdacVersion = '6.90.0.56';
Using "About ODAC" yields "6.90.0.56 for RAD Studio 2009"
Using "About Unidac" yields "3.00.0.7 for RAD Studio 2009"
BTW: Is it possible to provide functions in Ora.pas, that return the OdacVersion and DacVersion, instead of using constants? When using packages, the "reported" version will differ from actual version since the compiler will "resolve" the constant at compile time!
-
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53
Hi Challenger,
Is this the intended behavior, or is it a bug in design time? In my opinion the DefaultExpression should get filled in, regardless of the Active-State of the query in design time.
Thats it! If the query is open at the time when the persistent fields get created, then default expression is filled in. If I choose to create all fields in design time with query.active = false, defaultexpression is not filled in.Challenger wrote:Please try to Open a query in design time and then create persistent fields.
Is this the intended behavior, or is it a bug in design time? In my opinion the DefaultExpression should get filled in, regardless of the Active-State of the query in design time.
Hello
Part of the information about a field is available after opening the server cursor only. Therefore we get the information about the default field value after server cursor is open (after you call the Open method). Now we are investigating the possibility of filling default field values before it. If it is possible we will implement it certainly.
Part of the information about a field is available after opening the server cursor only. Therefore we get the information about the default field value after server cursor is open (after you call the Open method). Now we are investigating the possibility of filling default field values before it. If it is possible we will implement it certainly.
-
- Posts: 4
- Joined: Fri 23 Jan 2009 20:05
News
Hello Bork any news about this investigation?