daft-development — For discussing the development of DaFT

[Daft-development] Re: XLS Error

[Jelco H. <daf...@it...>]

Hi Bruno,

I have been able to reproduce this problem. It occurs when the upper left=
 cell
contains an integer. Time permitting, I'll put a fixed version on the net=
 at
the the of the day or else tomorrow.

Jelco.

Citeren Bruno Almeida do Lago <teo...@gm...>:

> Hello,
>
>
>
> I'm using fishing tool to export sql queries directly into XLS files
> (default file format for the analysts).
>
>
>
> Today after running a very simple query one analyst reported a data
> inconsistency inside the XLS file. Please, check the attached print scr=
een:
>
>
>
>
>
> As you can see, PROC_ID is right in fishing tool screen (338638), but a=
t XLS
> its wrong (10958).
>
> I've downloaded the latest version (1.4.1), but got the same error.
>
> Exporting in CVS is all right!
>
> The table is:
>
>
>
>
>
> Nome                                      Nulo?    Tipo
>
>  ----------------------------------------- --------
> ----------------------------
>
>  PROC_ID                                   NOT NULL NUMBER(10)
>
>  PREST_ID                                           NUMBER(5)
>
>  PROC_MES                                  NOT NULL DATE
>
>  PROC_PROTOC_DT                            NOT NULL DATE
>
>  PROC_VCTO_DT                              NOT NULL DATE
>
>  PROC_STATUS                               NOT NULL VARCHAR2(1)
>
>  PROC_CONTA                                         VARCHAR2(17)
>
>  PROC_NR_FAT                                        VARCHAR2(10)
>
>  COD_USU                                            NUMBER(5)
>
>  BANCO_ID                                           NUMBER(4)
>
>  AGENC_ID                                           NUMBER(5)
>
>  MOV_TIPO_ID                               NOT NULL NUMBER(3)
>
>  PROC_STATUS_DT                            NOT NULL DATE
>
>  PROC_IMP                                           NUMBER(3)
>
>  PROC_FORM_PG                              NOT NULL VARCHAR2(1)
>
>  PROC_TIPO_ATEND                                    VARCHAR2(1)
>
>  PROC_TIPO                                 NOT NULL VARCHAR2(1)
>
>  PROC_GLOSA_OR                                      NUMBER(10)
>
>  PROC_GLOSA_DEST                                    NUMBER(10)
>
>  PROC_PCH_GER                                       VARCHAR2(1)
>
>  PROC_URGENCIA                                      VARCHAR2(1)
>
>  PROC_IMP_DT                                        DATE
>
>  PROC_INC_DT                                        DATE
>
>  BORD_ID                                            NUMBER(10)
>
>  BORD_MES                                           DATE
>
>  PROC_OBS                                           VARCHAR2(80)
>
>  PROC_GERACAO                                       VARCHAR2(1)
>
>  PROC_ETIQUETA                                      VARCHAR2(1)
>
>  PROC_ANALISTA                                      NUMBER(5)
>
>  PROC_ANALISTA_DT                                   DATE
>
>  PROC_PCH_GER_CONTAB                                VARCHAR2(1)
>
>  GRP_EMP_ID                                NOT NULL NUMBER(2)
>
>  PROC_VALORIZA                                      VARCHAR2(1)
>
>  PROC_REC_OR                                        NUMBER(10)
>
>  PROC_ENVIO_TSR_DT                                  DATE
>
>  PROC_PRED_COD                                      NUMBER(6)
>
>  PROC_CH                                            NUMBER(8,4)
>
>  PROC_CONTA_DGT                                     VARCHAR2(2)
>
>  PROC_ENVIO_TSR_NR                                  NUMBER(3)
>
>  PROC_QTD_HRA_TRAB                                  NUMBER(6)
>
>  PROC_STA_PRL                                       VARCHAR2(1)
>
>  PROC_OBS_PRL                                       VARCHAR2(200)
>
>  PROC_USR_AUT_PGT                                   VARCHAR2(10)
>
>  PROC_DAT_AUT_PGT                                   DATE
>
>  PROC_USR_ICS                                       VARCHAR2(15)
>
>  PROC_DAT_ICS                                       DATE
>
>  PROC_DES_TIP_PGT                                   VARCHAR2(30)
>
>
>
> Best Regards,
> Bruno
>
>
>
>

[Daft-development] Known issues and future improvements

[Jelco H. <DaF...@it...>]

Hi all,

It has been a few weeks ago when daft version 1.2.1 has been released. Till so 
far I haven't found any major bugs. If you find one, please let me know. One 
minor bug I found is the absence of the tool tip on the clear table buttons.
Another issue is the format of the auto generated update and insert statements 
when you click on Ctr-u or Ctr-i. I still have to edit it too much before 
it's of any use. Let me know any suggestions for improving it. 

The windows version was the first distribution that appeared, then followed 
the Suse 9.1 en Fedora 3 Linux rpm's, both of them include a binary version 
of the tclodbc library compiled against unixODBC version 2.2.10-1. A Mac OS X 
version is in the making. The structure of the kit file, tclkit and the odbc 
library is sketched in this document: 
http://www.itft.net/daft/daft_architecture.pdf. 

Which brings me to the subject of the new http://www.itft.net web page, fully 
dedicated to the database fishing tool, altough not complete yet.

In DaFT Version 1.3 the main focus will be on the possibility of exploring 
other database objects as tables and views as well. This means for each 
database type a description is needed what kind objects can be found (primary 
keys, foreign keys, constraints, triggers, procedures, functions, 
packages..,), how to retrieve them, and how to present them (table, text, 
colored columns, explorer view).  I will not implement all object types at 
once, but I probably need to refactor the multicolumn listbox and the tabbed 
views, and set up a XML based description of the database objects 
understandable by daft.
One option would be to use the tile (tkTable project) objects, and get a nice 
skinned user interface on top of it.

- Jelco