Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2004
    Posts
    91

    Unanswered: Unsupported datatype issue

    Hi everyone -

    Last night my queries were working fine, this am the DBA's added a new column to the tables.

    The column type is ST_GEOMETRY

    When my code runs....

    Code:
            sqlQuery = "SELECT * FROM lrcreator.politicalbasins ORDER BY BASINNAME";
            xx = cs.GetLandACQConnectionString();
            DS = new DataSet();
            OConn = new OracleConnection(xx);
            ODA = new OracleDataAdapter(sqlQuery, OConn);
            ODA.MissingSchemaAction = MissingSchemaAction.AddWithKey;
            ODA.Fill(DS, "ALL_BASINS");
            OConn.Close();
    The code fails at ODA.Fill with an exception of unsupported datatype....


    What do i need to do to get the system running again

    thanks
    tony

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    You are paying the price for lazy coding tehnique by using the "*" in the SELECT statement.
    Replace it with appropriate column names & it will work again.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    Or else
    Code:
    ALTER TABLE lrcreator.politicalbasins SET UNUSED COLUMN ST_GEOMETRY
    Beware of this though, see this link.

  4. #4
    Join Date
    Oct 2004
    Posts
    91
    Quote Originally Posted by anacedent
    You are paying the price for lazy coding tehnique by using the "*" in the SELECT statement.
    Replace it with appropriate column names & it will work again.

    WOW - what a great idea...

    do you think that maybe i made the post a little shorter
    by NOT listing all the fields that are returned... HUH, maybe???

    AND that i had already tried that??? HUH, maybe??
    (gawd, troll posts make me sick)

    just as an FYI - it fails using the name of the field.

    I've placed an support call to Oracle, and the first response
    was to update the ODP.net driver - typical, usually the first
    response is to reboot, but this one was a little different.

    more as it becomes available

  5. #5
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    Quote Originally Posted by alt-088
    WOW - what a great idea...

    do you think that maybe i made the post a little shorter
    by NOT listing all the fields that are returned... HUH, maybe???

    AND that i had already tried that??? HUH, maybe??
    (gawd, troll posts make me sick)

    just as an FYI - it fails using the name of the field.

    I've placed an support call to Oracle, and the first response
    was to update the ODP.net driver - typical, usually the first
    response is to reboot, but this one was a little different.

    more as it becomes available
    You are totally out of line. You indicated that you used "select *" how was anacdent supposed to know that that was not what you actually used. Yes, she has a sharp tongue, but I thought the same thing and was about to make the same suggestion before I finished reading the rest of the post. Unless you need the new column, why are you including it in your procedure. If you don't select it, your web page will not care what the column type is.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •