Subject | Re: [firebird-support] How would Firebird prevent users thrasing database |
---|---|
Author | Nando Dessena |
Post date | 2004-04-06T12:08:12Z |
Johan,
J> From Clarion NG
this ping-pong is really starting to confuse me. If people from the
clarion or whatever other group want to talk with people here, why
don't they subscribe? It won't cost a dime and there's a news
interface included.
I cannot make a sense of these threads, I hope others are
more able than me and that you get the required answers anyway.
Whatever, hijacking other threads is very bad netiquette to me, and
doesn't contribute to develop a positive attitude in the reader.
Anyway...
J> You cannot have 100% protection but you can make it difficult by using the
J> external name attributes of tables & columns. In other words, the Column
J> labels
J> defined in the Clarion Dictionary and used in the Clarion program can be
J> meaningfull labels whereas the external names could be cryptic ones like
J> T001,
J> T002, etc for tables and C001, C002, etc for Columns. It would take somebody
J> a
J> bit of time to unravel the database. This has a down side to it as it will
J> make
J> it difficult for you when querying the database using Query tools or SQL
J> utilities as the names on the SQL backend would be cryptic (unless you can
J> memorize all the backend names of columns & tables). You would just have
J> build
J> in all the functionality you need into your programs.
I have no other word than "paranoia" to describe this.
"Fighting windmills" would also be somehow appropriate. ;-)
Ciao
--
Nando Dessena
mailto:nandod@...
J> From Clarion NG
this ping-pong is really starting to confuse me. If people from the
clarion or whatever other group want to talk with people here, why
don't they subscribe? It won't cost a dime and there's a news
interface included.
I cannot make a sense of these threads, I hope others are
more able than me and that you get the required answers anyway.
Whatever, hijacking other threads is very bad netiquette to me, and
doesn't contribute to develop a positive attitude in the reader.
Anyway...
J> You cannot have 100% protection but you can make it difficult by using the
J> external name attributes of tables & columns. In other words, the Column
J> labels
J> defined in the Clarion Dictionary and used in the Clarion program can be
J> meaningfull labels whereas the external names could be cryptic ones like
J> T001,
J> T002, etc for tables and C001, C002, etc for Columns. It would take somebody
J> a
J> bit of time to unravel the database. This has a down side to it as it will
J> make
J> it difficult for you when querying the database using Query tools or SQL
J> utilities as the names on the SQL backend would be cryptic (unless you can
J> memorize all the backend names of columns & tables). You would just have
J> build
J> in all the functionality you need into your programs.
I have no other word than "paranoia" to describe this.
"Fighting windmills" would also be somehow appropriate. ;-)
Ciao
--
Nando Dessena
mailto:nandod@...