i installed PostgreSQL 12 at mac mini and i will connect from my windows pc with a xojo app.
first error was
FATAL: no pg_hba.conf entry for host “192.168.178.35”, user “software”, database “markus”, SSL off
please can give someone me a working configuration pg_hba.conf tip?
that Xojo work and pgAdmin4 too.
that postmaster.pid appear for a second and disappear in interval of 5 seconds.
before i changed something i used copy / paste for pg_hba.conf & postgresql.conf
seems after copy it back it have other permissions … arrgg
i add postgree user for this files and i think the server is running now.
I created table objects using pgAdmin and i wrote table name and column names uppercased. pgAdmin created query with quotas - because of the names was uppercased. So query had to be written with quotas.
that seem to be a limitation of the GUI data grid editor in pgAdmin. You can insert data without a PK by other means, if you like.
sure, if public is in your search_path (which it is by default), you can specify just "Table1". The quotes are mandatory as long as the table has a name that does not comply with the usual naming rules of an identifier: [a-z_][a-z0-9_]* . Internally, all non-quoted identifiers are converted to lower case, so AbC is just an alias of abc as is aBc but different to "Abc". pgAdmin again ‘helps’ here by quoting the table name in the CREATE TABLE statement if you use the GUI and enter an titlecased name.
See here: https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS
you can do that even easier w/o specifying the network by using a samenet rule: host all all samenet md5
with that, all hosts on the networks the server is itself listing to (see listen_addresses parameter in postgresql.conf) will be allowed to connect as all users to all databases without SSL identified by an hashed password.
have a look to the listen_addresses GUC mentioned before. It often default to localhost meaning the server does only listen on the loopback interface and is therefore not accessible from other hosts at all.
it does, but you need a working reverse lookup (PTR) DNS configuration for this to work.
These ‘stupid’ rules are required by the SQL standard (handy grammar excerpt), dating back at least till SQL-92 (Quote from a draft of the standard):
4) An <SQL language identifier> is equivalent to an <SQL language
identifier> in which every letter that is a lower-case letter
is replaced by the equivalent upper-case letter or letters. This
treatment includes determination of equivalence, representation
in the Information and Definition Schemas, representation in the
diagnostics area, and similar uses.
You can absolutely use “Pascal Casing” in your queries:
both statements will operate on a field mytable.pascalcaseid (downfolded as identifiers are not quoted). The behaviour of PostgreSQL to downfold identifiers instead of upfolding them as mentioned in the standard is just an implementation detail, the required equivalence is given nevertheless.
ok, that sounds good.
in ms sql i can use Pascal Casing at design with few exceptions. (reserved words need brackets in query.)
i used show search_path
it show “$user”, public
my issue was this Uppercase thing at Table Design.
i used Table1 in query then i got an error then i changed it to public.Table1 got error then to public.“Table1”
but now i can just use Table1 if the schema table name is table1
