At 17:27 3/4/2006, you wrote:

Sure, but what I understood from Bram, some other Timestamp/Datetime
fields were working, only this particular sort of Timestamp isn't.

If you think carefully you'll conclude that there is only one type of TIMESTAMP: day, month, year, hours, minutes, seconds and 1/1e6 of seconds. All other types are derived from this format, the complete TIMESTAMP format.


> >Another thought on the problems Arí has with
> >update queries and TODBCConnection: as I need
> >only read access, I never implemented UpdateIndexDefs; might that be required?
>
> UpdateIndexDefs? What is the function of such
> method? Since data base manager ever keep the
> index(es) up-to-date and it has the index(es)
> description in its areas, I can't imagine...

To let modifications things work automatically, it is needed. This
function updates the information about the indexes on the table. From
this information it derrives what the primary key is. And the where part
of the update/insert/delete statements is depending on the primary
key... But you could also 'manually' add all fields-definitions, and
then set the field that should be used in the where-clause of the sql-
statement.

I insist: management of indexes, primary keys, etc. are function of database manager. It administrates indexes, keys(primary and others), triggers and so on. I can't understand how you insist a treat these fields... Excuse me.
Can you imagine if each programmer that accesses a DB2 table has power to treat indexes, keys and similar? How will these database be after one week? And after one month? At the end of the year. The internal attributes of the tables are protected from direct access of application programs. DB2 RDBMS make calculations of access paths, type of access, define access algorithms using the information of indexes and keys. It's important to remeber: The RDBMS do this.


I'm not sure about that. The developer is asking for a Date/time, so
he'll expect that he'll get a Date/time.
If you need a string from DB2, I would use a cast in the sql-statement.

I'm sure that if TIMESTAMP returns a string [26] any programmer can edit and transform this string as needed.

If a developer is asking for a date/time format is easy: Convert it to date/time.

You can treat these fields as you want. I suggest a string [26] because it seems to be more simple(I confess I have no idea how the interface is programmed and in which language). However if you INSERT and UPDATE rows in a table and a COBOL programmer(for example) access this table and find the format he expects(containing the fields I mentioned above), no problema!

Regards

Arí

Reply via email to