|
...as opposed to the usual fallback DECLARE @key LONG VARCHAR? |
The forum will be down for maintenance at some point from Friday, November 16 at 19:00 EDT until Sunday, November 18 at 23:59 EDT. Downtime will be minimized but the exact timing is unknown.
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, 15:23
question was seen: 50 times
last updated: 22 Oct, 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.