Modification Observing Not Working

Feb 17, 2008 9:26pm

thinkcl 6 post(s)

So I finally gt everything wired up, ran the assistant and enabled a simple table with a primary key and a title column. The added a few rows of data. Hooked up a simple GUI and ran it. I am getting back the following error message through NSError.LocalizedFailureReason . . .

Table product in schema public has not been prepared for modification observing.

I checked and the BaseTen tables and triggers etc are in the database and as I said the BaseTen assistant shows that the tables are enabled. Could it be my PostgreSQL configuration?

Feb 20, 2008 6:28pm

thinkcl 6 post(s)

Hello, anybody here? Guess I will try Apple discussions.

Feb 21, 2008 1:03pm

Tuukka Norri Administrator 11 post(s)

Hi!
I can’t say for certain what could have caused this. My first thought was that the problem would be with BaseTen Assistant. We had already had thought about making its source part of the GPL’d distribution thus speeding up its bug resolution process.

Another cause could be that if you created the data model using Xcode, it prefers capitalized the entity names. Table names, on the other hand, are case-sensitive in Postgres. Try using the name Product for the entity in IB.

Having two Postgres installations could cause this but I doubt that it would be the case.

If you want, you could try creating the BaseTen tables without the assistant, if you are using BaseTen version from SVN trunk. First remove the BaseTen schema, in case the assistant has installed an out-of-date version, using this command in psql: DROP SCHEMA baseten CASCADE;. Then follow the instructions in http://www.karppinen.fi/baseten/wiki/PreparingDatabasesWithoutAssistant

If it doesn’t work out, I’ll come up with something else.

Feb 21, 2008 8:43pm

thinkcl 6 post(s)

Tuukka,

Thanks for the reply. It may well be the PostgreSQL install. I am on Leopard and used a package installer for PG 8.2.5 and noticed some strange behavior after the install – mostly permission issues. I come from a MySQL background and am finding PosgreSQL very difficult to install and administer. Will try and resolve PosgreSQL issues first.

Thanx again.

Feb 23, 2008 12:07am

Tuukka Norri Administrator 11 post(s)

I guess it depends on what one is used to :) I like Postgres better. MySQL is easier to upgrade, though, since they don’t change the database file format with every new version like some others do…

If the problem was indeed with the database, then I’d suppose that your tables would be in two different installations but would be BaseTen enabled in only one of them. This doesn’t make much sense but I guess there might be some other problem that I can’t come up with right now.

Anyway, I’d check that the table names match exactly – you can get the table list with the command \d in psql and of course with BaseTen Assistant.

MK&C Forum

Modification Observing Not Working

Voices

Feb 17, 2008 9:26pm thinkcl 6 post(s)	So I finally gt everything wired up, ran the assistant and enabled a simple table with a primary key and a title column. The added a few rows of data. Hooked up a simple GUI and ran it. I am getting back the following error message through NSError.LocalizedFailureReason . . . Table product in schema public has not been prepared for modification observing. I checked and the BaseTen tables and triggers etc are in the database and as I said the BaseTen assistant shows that the tables are enabled. Could it be my PostgreSQL configuration?

Feb 20, 2008 6:28pm thinkcl 6 post(s)	Hello, anybody here? Guess I will try Apple discussions.

Feb 21, 2008 1:03pm Tuukka Norri Administrator 11 post(s)	Hi! I can’t say for certain what could have caused this. My first thought was that the problem would be with BaseTen Assistant. We had already had thought about making its source part of the GPL’d distribution thus speeding up its bug resolution process. Another cause could be that if you created the data model using Xcode, it prefers capitalized the entity names. Table names, on the other hand, are case-sensitive in Postgres. Try using the name Product for the entity in IB. Having two Postgres installations could cause this but I doubt that it would be the case. If you want, you could try creating the BaseTen tables without the assistant, if you are using BaseTen version from SVN trunk. First remove the BaseTen schema, in case the assistant has installed an out-of-date version, using this command in psql: DROP SCHEMA baseten CASCADE;. Then follow the instructions in http://www.karppinen.fi/baseten/wiki/PreparingDatabasesWithoutAssistant If it doesn’t work out, I’ll come up with something else.

Feb 21, 2008 8:43pm thinkcl 6 post(s)	Tuukka, Thanks for the reply. It may well be the PostgreSQL install. I am on Leopard and used a package installer for PG 8.2.5 and noticed some strange behavior after the install – mostly permission issues. I come from a MySQL background and am finding PosgreSQL very difficult to install and administer. Will try and resolve PosgreSQL issues first. Thanx again.

Feb 23, 2008 12:07am Tuukka Norri Administrator 11 post(s)	I guess it depends on what one is used to :) I like Postgres better. MySQL is easier to upgrade, though, since they don’t change the database file format with every new version like some others do… If the problem was indeed with the database, then I’d suppose that your tables would be in two different installations but would be BaseTen enabled in only one of them. This doesn’t make much sense but I guess there might be some other problem that I can’t come up with right now. Anyway, I’d check that the table names match exactly – you can get the table list with the command \d in psql and of course with BaseTen Assistant.