SQLite Problems: Simulator copy + first value of every query is mumbo-jumbo

[Norbert]

Hi,

I saved constant values into a table of a SQLite3 database. I've done this via Terminal. Then I filled the table with some values. The database is set up all right: Queries in Terminal and in DB inspectors like 'SELECT * FROM myTable' return all values and they are all right.
I added the database file into my XCode project.
Now I've got two problems:


The first one: When I click on 'Build & Go' the database file isn't copied correctly into the iPhone simulator directory. sqlite3_prepare_v2() returns ERROR 1 and opening the database file manually gets me an error too.
If I copy the original database file from the project directory into the simulator's application directory then sqlite3_prepare_v2() works.
Unlike Apple's SQLBook example, my code doesn't make a copy of the DB explicitly as I don't need an editable copy of it. I just want to read values out of it.

Is this a bug or a...



My second problem: When I drop off queries like 'SELECT name FROM Constants' in Terminal, I get all the values and all are correct (like mentioned above).
But when I do this in my code:

CONNECTION EXISTS...

const char *sql = "SELECT name FROM Constants";
sqlite3_stmt *statement;
if (sqlite3_prepare_v2(database, sql, -1, &statement, NULL) == SQLITE_OK) {
  // We "step" through the results - once for each row.
  while (sqlite3_step(statement) == SQLITE_ROW) {
    // The second parameter indicates the column index into the result set.
    char *name = (char*)sqlite3_column_text(statement, 0);
  }
}

The first result is ALWAYS:

[\x8bU\x10\x8d\x83`

The following names are all correct but the first one is a mess. I've already created a brand new database file with a new table and other values. Same errornous value.


Has someone experienced a similar problem one day and found the solution to this?

[PhoneyDeveloper]

Does your database file that's being copied by Xcode have a file extension? You should look at the build transcript and see how Xcode is copying it. In the build window there are several little icons on the left side in the middle. Click on the one that looks like a page of text. It's possible that Xcode thinks it's some other kind of file than it really is and is processing it somehow when it copies it.

[Norbert]

Originally Posted by PhoneyDeveloper

Does your database file that's being copied by Xcode have a file extension? You should look at the build transcript and see how Xcode is copying it. In the build window there are several little icons on the left side in the middle. Click on the one that looks like a page of text. It's possible that Xcode thinks it's some other kind of file than it really is and is processing it somehow when it copies it.

Hm, don't know what icons you mean. In my build window are "Building target..." and "Checking dependencies" and "Build succeeded", nothing else.
I tried both .db and .sql as file extensions and there was no difference.

[PhoneyDeveloper]

These icons. Click on the third one from the left.

[Norbert]

Thank you for posting this image

I found out that I was a little lazy when reading Apple's example: I didn't open the bundled DB but the one in the application folder. Because I haven't copied it in there first it gave me an error when trying to open it. I didn't realize my fault because it created the file in the Documents directory because it was not there. And I thought that creating a temporary copy is standard behaviour.
So this solves my first problem.

But the second one is still occuring. Any thoughts?