InitSpatialMetaData question

[Andrea P.]

Hi,

I read the news about 3.0.2.
expecially for new InitSpatialMetaData() initializatio system.

I don't understand what happened when I do:

>spatialite new_db.sqlite

Actually I have a newly created DB with the tables inizialized.

Is this also with the 3.0.2 or I need to call a my sql to popolate the
spatial_ref_sys table ?

Is possible when ask for a new db add also a script sql to execute
something like this

spatialite "my_new_db.sql " "my_startup_script.sql"


Thx,

[a.fu...@lqt.it]

Hi Andrea,

> I don't understand what happened when I do:
>
> >spatialite new_db.sqlite
>
> Actually I have a newly created DB with the tables inizialized.
> Is this also with the 3.0.2 or I need to call a my sql to popolate
> the spatial_ref_sys table ?
>

absolutely yes; nothing changes for spatialite CLI
and spatialite_gui tools.
both them will bahave exactely as before.

the new approach introduced in 3.0.2 was strongly
supported by developers interested on smart phones,
tablets and other limited capabilities mobile devices
[Android and alike]. i.e. when each single byte
of storage could make the difference.

for standard Linux/Win desktops and laptops I see no good
reason suggesting to diverge from the well established
traditional bahaviour already supported by any previous
release.

> Is possible when ask for a new db add also a script sql to execute
> something like this
>
> spatialite "my_new_db.sql " "my_startup_script.sql"
>

this is already supported: you simply have to pass your
SQL-script on the standard input. e.g.:

# spatialite my_new_db.sqlite <my_startup_script.sql

the spatialite task will then create the new DB, execute
the initialization script then terminating.

# spatialite my_new_db.sqlite

now you can start your interactive work session;
any required preliminary initialization step
has already been performed into the previous step

bye Sandro