Error (ERROR_STORAGE_FAILURE)
|
cdakin
Joined: 2003-04-30
Posts: 1 |
Posted: Wed, 2003-04-30 20:27
|
|
After I have gone through the setup and returned to the main.php I am getting the following error. in C:Inetpubwwwrootgallery1gallery2modulescoreclassesGalleryStorageDatabaseStorage.class at line 1072 Can Anyone help? Thank You, |
|
Posts: 11
same sort of problem for me ...
Error (ERROR_STORAGE_FAILURE)
in modules/core/classes/GalleryStorage/DatabaseStorage.class at line 1434
in modules/core/classes/GalleryStorage/DatabaseStorage.class at line 1327
in modules/core/classes/GalleryStorage/DatabaseStorage/PostgreSqlDatabaseStorage.class at line 143
in modules/core/module.inc at line 262
in init.php at line 162
in main.php at line 99
in main.php at line 46
i use a postgres db
the queries generated to create table seems very strange ... :smile
extract from gallery debug log:
######################
CREATE TABLE GalleryDerivativeImage (
id
INTEGER
NOT NULL
,
width
INTEGER
,
height
INTEGER
) &nbsp; <code></code>
<hr />
2003-05-01 21:10:54 [<no session id>] <hr />
(postgres7): CREATE INDEX GalleryDerivativeImage_id
ON GalleryDerivativeImage
(id) &nbsp; <code></code>
<hr />
2003-05-01 21:10:54 [<no session id>] <hr />
(postgres7): INSERT INTO Schema (
name,
major,
minor
) VALUES (
'GalleryDerivativeImage',
1,
0
) &nbsp; <code></code>
<hr />
CREATE TABLE GalleryDerivativePreferencesMap (
itemId
INTEGER
,
order
INTEGER
,
derivativeType
INTEGER
,
derivativeOperations
VARCHAR(
255
)
) &nbsp; <code></code>
<hr />
<br>
<b>Warning</b>: PostgreSQL query failed: ERROR: parser: parse error at or near "order"
in <b>/var/www/html/gallery2/lib/adodb/drivers/adodb-postgres64.inc.php</b> on line <b>454</b><br>
ERROR: parser: parse error at or near "order"
: ERROR: parser: parse error at or near "order"
##########
extract from postgres log:
###########
[mat@matounet mat]$ cat /var/log/postgres.log | grep CREATE -5 | more
}
2003-05-01 11:05:36 [5062] DEBUG: ProcessUtility: set datestyle='ISO'
2003-05-01 11:05:36 [5062] DEBUG: CommitTransactionCommand
2003-05-01 11:05:36 [5062] DEBUG: StartTransactionCommand
2003-05-01 11:05:36 [5062] DEBUG: query:
CREATE AGGREGATE BIT_OR
(
basetype = bit,
sfunc = bitor,
stype = bit
)
--
:limitCount <>
:setOperations <>
:resultRelations ()
}
2003-05-01 11:05:36 [5062] DEBUG: ProcessUtility:
CREATE AGGREGATE BIT_OR
(
basetype = bit,
sfunc = bitor,
stype = bit
)
--
2003-05-01 11:05:36 [5061] DEBUG: StartTransactionCommand
2003-05-01 11:05:36 [5061] DEBUG: query: -- This file was automatically generated from an XSL template, which i
s
-- why it looks so ugly. Editing it by hand would be a bad idea.
--
CREATE TABLE Schema (
name
VARCHAR(
128
.......
##############"
ok
sorry for this long post
i'll try to update php...
thx for any idea
Mat
Posts: 7994
cdakin:
Can you turn on debug mode in config.php and then look through the debug results and post a summary of anything that looks like an error message? Or better yet, capture all the results into a .txt or .html file and post a link to it here?
Posts: 7994
matounet,
You've got a different problem. It looks to me like you got rid of the $storageconfig['columnPrefix'] setting in your config.php which is why
your columns are appearing like "itemId" and "order" instead of "g_itemId"
and "g_order". Since order is a reserved word in PostgresQL,
this isn't gonna work for you. You have to put *some* prefix there.
Posts: 11
thx Bharat
i put the prefix right, but it seems not better ... :/
the last logs:
http://matounet.dyndns.org/gallery2.txt
http://matounet.dyndns.org/postgres.txt
and my config.php :smile:
http://matounet.dyndns.org/config.txt
Posts: 7994
Ah, ok now you're getting a different problem, one that I had not anticipated.
Some versions of Postgres have a 32 byte limit on table length, and some of
my table names exceed that limit.
I'm going to look into figuring out a way to reduce the length of my table
names, but in the meantime, you might look into ways to disable that limit
(I don't exactly know how to do it, but my Postgres install doesn't have it).
-Bharat
Posts: 7994
Ok, I just checked in a change that drops the "Gallery" prefix from all table names. This brings all the table names in under the 32 character limit imposed by Postgres so you should get by this problem.
You'll need to completely clean out your existing G2 install to use the new stuff (delete all your gallery data files and get rid of any tables in your database).
Posts: 11
still same errors whith the new version ... :/
and to change the table name length, i have to recompile postgres :sad:
any other idea ? :smile:
Posts: 11
Ok ok
i'll try to recompile tonight whith postgres 7.3, the
NAMEDATALEN is 64 by default ...
to be continued ..
Posts: 11
three hours later ...
finally that's work !! ... with postgres 7.3.2 .
thank you for your precious help Bharat, long life to G2 !
...and sorry for my english. :grin: