Hi Marcel,
> I already checked these two SQL Functions. And I already tried them,
> but I think they dont work?
> Especially I considered RecoverGeometryColumn(). I think it should
> work.
>
both AddGeometryColumn() and RecoverGeometryColumn() are the foundation
pillars sustaining all the SpatiaLite architecture.
so you should always safely assume that they are surely working as
they are intended to work, and if something goes wrong this certainly
means that you are using them in the wrong way.
> My table has a column geometry with BLOB sz = 228 GEOMETRY.
> Maybe it is the problem that the type of this columns is empty... no
> type and not BLOB. But I dont understand why this got changed by my
> sql-query... because before the type in the virtual table is BLOB.
>
every GEOMETRY is a BLOB, but not all BLOBs are GEOMETRIES.
spatialite_gui correctly reports "BLOB sz = 228 GEOMETRY"
because it has detected that this BLOB actually encapsulates
a valid Geometry value.
anyway, until you don't appropriately register the Geometry
column within the metadata tables (the specific task performed
by AddGeometrtColumn and/or RecoverGeometryColum) spatialite
will refuse to recognize this column as a "genuine geometry".
if you are using spatialite_gui the simplest approach you can
adopt is the following one (please see the attached figures):
a) right click on the geometry column; a context menu will appear
b) first check the column, so to discover its SRID, Type and Dims
c) and finally use the Recover dialog so to register the column;
    you need to exactly insert the same identical values ad reported
    by the Check tool
you could obviously get the same result directly using some
SQL statement, but using the GUI tools is surely easier ;-)
bye Sandro