|
...as opposed to the usual fallback DECLARE @key LONG VARCHAR? |
The forum is currently being migrated to a new host. While the migration happens, the old server is still available. Once the new machine is ready, I will copy the database to the new machine. Feel free to ask and answer questions in the meantime.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 21 Oct '18, 15:23
question was seen: 380 times
last updated: 22 Oct '18, 03:10
Hm, according to the underlying an_unload_db structure, it's a C "const char*", and the v17 topic on "Security: Keys for encrypted databases" says
So I guess LONG VARCHAR is appropriate.
Nevertheless, it's astonishing that the data type is not explicitly mentioned for functions like ENCRYPT.