Opened 20 years ago
Closed 20 years ago
#272 closed defect (fixed)
DBSeries returns no named series
Reported by: | César Pérez Álvarez | Owned by: | danirus |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | DataBase | Version: | head |
Severity: | major | Keywords: | |
Cc: |
Description
If we try this code
Real DBOpen("mydatabase", "myuser", "mypassword");
Set mySet = DBSeries("
select cast(id_date as datetime) as id_date, value
from
(
select '2003-01-01' as id_date, 1 as value union
select '2003-01-02' as id_date, 1 as value union
select '2003-01-03' as id_date, 1 as value union
select '2003-01-04' as id_date, 1 as value union
select '2003-01-05' as id_date, 1 as value union
select '2003-01-06' as id_date, 1 as value union
select '2003-01-07' as id_date, 1 as value union
select '2003-01-08' as id_date, 1 as value union
select '2003-01-09' as id_date, 1 as value union
select '2003-01-10' as id_date, 1 as value
) DATA
order by id_date", Diario, SetOfText("MySerie"));
Real DBClose("mydatabase");
in SQLServer or
Real DBOpen("mydatabase", "myuser", "mypassword");
Set mySet = DBSeries("
select to_date(id_date, 'YYYY-MM-DD') as id_date, value
from
(
select '2003-01-01' as id_date, 1 as value from dual union
select '2003-01-02' as id_date, 1 as value from dual union
select '2003-01-03' as id_date, 1 as value from dual union
select '2003-01-04' as id_date, 1 as value from dual union
select '2003-01-05' as id_date, 1 as value from dual union
select '2003-01-06' as id_date, 1 as value from dual union
select '2003-01-07' as id_date, 1 as value from dual union
select '2003-01-08' as id_date, 1 as value from dual union
select '2003-01-09' as id_date, 1 as value from dual union
select '2003-01-10' as id_date, 1 as value from dual
) DATA
order by id_date", Diario, SetOfText("MySerie"));
Real DBClose("mydatabase");
in ORACLE, and we open the set mySet we can see that the serie inside is a no
named serie.
Change History (2)
comment:1 Changed 20 years ago by
Status: | new → assigned |
---|
comment:2 Changed 20 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This bug has been resolved, but I'm still waiting for a final decision about
which is the best solution to avoid exporting result Series to the Global Scope.
With the current code we can stop those exports doing DBSeriesMakeGlobal = 0,
but this approach was not commonly adopted by the community. Was one of the two
suggestions done.