Thread: Pls Help me: access problems to tables

Dear friends,

I logged on windows as a LAN user (so i'm not a domain user of the computer), then i installed postmaster, initdb and created database all under my LAN logon (which is yanyanc).

All went well! and i was able to run a script that i wrote which basically populates schema and all the tables for the database i just created.

then i tried to run another script which basically 'inserts' many records to the tables in the database that i've just created. but postgres seemed not to allow me to access any relations(tables). i tried select * from <relationname> and the <relationname> is always 'Not Found'. (But i've just inserted the relation and it can be viewed via PgAdmin!!!)

However when i use PGAdmin, and select the table i just created and then go to 'view data' then 'add', then i can add records one by one. However, it still won't allow me to load a script which inserts records.

I am wondering why aren't i allowed to access the tables/relations via 'select' and 'insert' statements while i am the owner of the database cluster, the database and all the tables?

i remembered that i once logged on as a domain/local user of the computer and did the same thing and i can insert records and select them without problem. my question is why would it be different when i create the db as a LAN login user? is there any way around it?

Thank you so much for your time and attention!

yours sincerely,

yan yan che

---

Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.

On Fri, 14 Mar 2003, [iso-8859-1] Yan Yan Che wrote:

>
> then i tried to run another script which basically 'inserts' many
> records to the tables in the database that i've just created. but
> postgres seemed not to allow me to access any relations(tables). i
> tried select * from <relationname> and the <relationname> is always
> 'Not Found'. (But i've just inserted the relation and it can be viewed
> via PgAdmin!!!)

Did you perhaps use mixed case (or upper case) when creating the name?
It's possible that PGAdmin created the table with double quotes around
the name at which point the name used without double quotes won't
match.