Aquileo | Recent changes to feature-requestshttps://sourceforge.net/p/gigabase/feature-requests/2003-03-11T20:11:29ZRecent changes to feature-requestsAquileo | Monitoring changes?2003-03-11T20:11:29Z2003-03-11T20:11:29ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net1dc0aea5287393b42c5f2597528a2c5ba1c352f3This is great work and very easy for use.
But for real use I need receive events about changing
objects.
How can I monitor object state change or changing their
values?
Best reards\!Aquileo | Compression2003-02-05T12:20:17Z2003-02-05T12:20:17ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.netdc6d83fabed9f77d60e57bc033d5a2917cc0a68bI think it would be a good idea to add internal
compression to the databaseAquileo | question about subsql - delete ...2002-07-15T08:16:20Z2002-07-15T08:16:20ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net252cd01845d1a582c7d2b06fca4483f962f50294Why didn't you support 'DELETE FROM <TblName>
WHERE <Conditioin>' clause?
There is any special reason?
If subsql.exe has that feature, It will be better.
Aquileo | "order by", dbReference<T>.?2002-04-06T05:13:36Z2002-04-06T05:13:36ZAndre Yarnoshttps://sourceforge.net/u/userid-507445/https://sourceforge.net4cc605118fa9407f9c799c0f36fb95da23985b5a
Hello.
I have been testing GigaBase \(version 2.58\) and I like
it. :-\)
I am interested in using the &quot;order by&quot; clause with
&quot;sort-parameter&quot; being:
\- a structure component accessed by dereferencing a
dbReference&lt;&gt;-type object using the dot notation.
I am also interested in using a &quot;sort-list&quot; made up of
several of the above &quot;sort-parameter\(s\)&quot;.
The following example illustrates this:
// \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
// ExampleCode \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
// \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# START
class Contract;
class Detail
\{
public:
real4 weight;
dbArray&lt; dbReference&lt;Contract&gt; &gt; contracts;
TYPE\_DESCRIPTOR\(\(KEY\(weight, INDEXED\),
RELATION\(contracts, detail\)\)\);
// \[1\]
static dbQueryExpression AscendingWeight\(
char\_t const\* NameOfDetailObject\)
\{
dbQueryExpression expr;
expr=dbComponent\(NameOfDetailObject,\_T\(&quot;weight&quot;\)\);
return expr;
\}
\}; // class Detail
class Contract
\{
public:
dbDateTime delivery;
dbReference&lt;Detail&gt; detail;
TYPE\_DESCRIPTOR\(\(KEY\(delivery, HASHED|INDEXED\),
RELATION\(detail, contracts\)\)\);
typedef dbCursor&lt;Contract&gt; dbCrsr;
static dbQueryExpression AscendingWeight\(\) // \[2\]
\{
return\( Detail::AscendingWeight\(&quot;detail&quot;\) \);
\}
\}; // class Contract
REGISTER\(Detail\);
REGISTER\(Contract\);
void RunQery\(\)
\{
Contract::dbCrsr contracts;
dbQuery q;
q = &quot;order by&quot;, Contract::AscendingWeight\(\); //\[3\]
if \( contracts.select\(q\) &gt; 0 \)
\{
do
\{
// ...
\}
while \( contracts.next\(\) \);
\}
\}
// \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# END
// ExampleCode \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
// \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#
The above classes \(Detail and Contract\) are from
testdb.cpp in the GigaBase distribution. These have
been modified as follows:
\- class &lt;Detail&gt; contains the static function
dbQueryExpression AscendingWeight\(char\_t const\*\);
which returns a &lt;dbQueryExpression&gt; to be used by a
&lt;dbQuery&gt; for sorting of records w.r.t. ascending
&lt;Detail::weight&gt;.
\- class Contract contains the &lt;dbCrsr&gt; typedef and
the static function:
dbQueryExpression AscendingWeight\(\) // \[2\]
which returns a &lt;dbQueryExpression&gt; to be used by a
&lt;dbQuery&gt; for sorting of &lt;Contract&gt;-type records
w.r.t. ascending &lt;Detail::weight&gt;.
The RunQery\(\) function above is an example of what I
am interested in achieving, but the
&lt;contracts.select\(q\)&gt; statement does not achieve the
required sorting.
I realise that, unlike the example code in the
GigaBase distribution, the
Contract::AscendingWeight\(\)
term in the query
q = &quot;order by&quot;, Contract::AscendingWeight\(\); // \[3\]
is associated with a dbReference&lt;&gt;-type
\(Contract::detail\) rather than a simpler \(non-
dbReference&lt;&gt;-type\) term like &lt;Contract::delivery&gt;.
I have checked the &quot;change-logs&quot; for GigaBase versions
2.59-2.61 and this issue is not addressed.
I have tried some &quot;hacks&quot; but have not been able to
resolve this issue myself \(lack of &quot;extensive&quot;
comments/implementation notes\).
If it were not a problem, I would be interested in
receiving detailed implementation notes about the
GigaBase code \(not mentioned in &quot;GigaBase
implementation issues&quot; section of documentation\) to
enhance my understanding of the code.
Any help would be greatly appreciated.
Cheers.
Andre
:-\)