Re: PHP Query Issues on Ingres R3 Linux Version

On Sep 11, 4:46 am, w1ndy <mattw...@xxxxxxxxx> wrote:
On Sep 10, 10:32 am, Grant Croker <grant.cro...@xxxxxxxxxx> wrote:



I guess you will find the answer more interesting...

demodb is owned by "ingres", the table was created by "userx" where that
is the username you executed the create table as. Since "userx" does not
own the database, your web/phppage needs to reference the table using
the schema prefix "userx", in effect "userx.page". See the highlighted
line inhttp://ingres.pastebin.com/d407bd1c1forwhat I mean.

regards

grant

On/El 10/09/08 18:53, w1ndy wrote/escribió:> Interesting... as you can see from my original post I did create a
table called "page", the error says the following...

Queryfailed with 2117 - Table 'page' does not exist or is not owned
by you.

--
Grant Croker - IngresPHP, Ruby and Python maintainer
The door was the way to... to... The Door was The Way. Good. Capital
letters were always the best way of dealing with things you didn't have
a good answer to.

Thanks Grant, that worked!!
It's nice to finally see some data =)
Yea you are right that is interesting, is it possible to set the table
permission to public, or do you always have to use "userx.table" ??

m@

If a table is owned by the DBA (the database owner) then there is no
need to proefix it by the owner (or schema) name. It's not a
"permission" thing so much as an object ownership issue.

An object which is not prefixed by a schema name is found by looking
for that object ownerd by the current user, and then owned by the DBA
(all subject to permission to use tha object). If such an object does
not exist after looking with those two owners, then it is considered
to not exist.

John
.

Relevant Pages

  • Re: Cross database update issue
    ... Also, for dbo-owned objects, the owner of both databases must be the ... You can execute sp_helpdb to determine the current database owners. ... > User Name: Test1 Role Name=Test ... > Role Test has select permission to table t_test ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Connection String
    ... I want to access a database which has a different owner. ... If this is SQL Server 2000, then I can guarantee you mean owner. ... Server 2005 or greater, you probably mean schema. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Permission for a role...
    ... Best regards ... The role db_dealer owns schema AT. ... Permission checking is bypassed for the object owner. ... should only have permission to connect to the database and execute stored ...
    (microsoft.public.sqlserver.security)
  • Re: Permission for a role...
    ... Permission checking is bypassed for the object owner. ... you should not specify a role as the schema owner if you want to prevent members of that role from using objects in the schema. ... And the role should only have permission to connect and execute stored procedures. ... The script below specifies a database user as the AT schema owner and grants EXECUTE permission on the AT schema to db_dealer members: ...
    (microsoft.public.sqlserver.security)
  • Re: SP accessing other db
    ... And its dbo user was blank even db Properties shows BUILTIN\Administrator as ... Now the database name is hard-coded. ... > with System Admin permission. ... >> have the same owner so that the dbo users map to the same login. ...
    (microsoft.public.sqlserver.security)