Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM SQL » View Thread |
Messages 1 to 8 of 8 total |
'encrypted with' and 'Union' |
Sat, Sep 24 2011 1:23 PM | Permanent Link |
JonD | I'm having trouble with the correct syntax for 'encrypted with' and
'union' select h.HHid GenID into junk from households h encrypted with 'junk' creates an encrypted table. but select h.HHid GenID into junk from households h union select i.Indid GenID from individuals i encrypted with 'junk' creates an unencrypted table. The encrypted with phrase seems to be ignored in the union case. It's probably something obvious JonD |
Sat, Sep 24 2011 7:39 PM | Permanent Link |
Raul Team Elevate | Jon,
This is just by looking at manual so might not work. However the manual it says "The WHERE, GROUP BY, HAVING, LOCALE, ENCRYPTED, and NOJOINOPTIMIZE clauses can be specified for all or some of the individual SELECT statements being joined with a UNION/EXCEPT/INTERSECT clause" Therefore it seems you're only encrypting the 2nd select - try select h.HHid GenID into junk from households h encrypted with 'junk' union select i.Indid GenID from individuals i encrypted with 'junk' |
Mon, Sep 26 2011 7:02 PM | Permanent Link |
JonD | Raul,
I'll give that a try... thanks JonD On 2011-09-24 7:39 PM, Raul wrote: > Jon, > > This is just by looking at manual so might not work. > > However the manual it says "The WHERE, GROUP BY, HAVING, LOCALE, ENCRYPTED, and NOJOINOPTIMIZE clauses can be specified for all or some of the individual SELECT statements being joined with a UNION/EXCEPT/INTERSECT clause" > > Therefore it seems you're only encrypting the 2nd select - try > > select h.HHid GenID > into junk > from households h > encrypted with 'junk' > union > select i.Indid GenID > from individuals i > encrypted with 'junk' > |
Mon, Sep 26 2011 7:08 PM | Permanent Link |
JonD | Raul
The simple solutions are the best! That worked Thanks, JonD On 2011-09-26 7:02 PM, Jon Lloyd Duerdoth wrote: > Raul, > > I'll give that a try... thanks > > JonD > > On 2011-09-24 7:39 PM, Raul wrote: >> Jon, >> >> This is just by looking at manual so might not work. >> >> However the manual it says "The WHERE, GROUP BY, HAVING, LOCALE, ENCRYPTED, and NOJOINOPTIMIZE clauses can be specified for all or some of the individual SELECT statements being joined with a UNION/EXCEPT/INTERSECT clause" >> >> Therefore it seems you're only encrypting the 2nd select - try >> >> select h.HHid GenID >> into junk >> from households h >> encrypted with 'junk' >> union >> select i.Indid GenID >> from individuals i >> encrypted with 'junk' >> |
Mon, Oct 3 2011 9:35 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jon,
<< creates an unencrypted table. The encrypted with phrase seems to be ignored in the union case. It's probably something obvious >> For UNION/EXCEPT/INTERSECT queries where you're dumping the contents into a table via INTO, you need to specify all result table modifiers in the *first* SQL statement where the INTO resides. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Oct 3 2011 5:17 PM | Permanent Link |
JonD | Tim,
So a second 'encrypted with' is ignored and is redundant? JonD On 2011-10-03 9:35 AM, Tim Young [Elevate Software] wrote: > Jon, > > << creates an unencrypted table. The encrypted with phrase seems to be > ignored in the union case. It's probably something obvious >> > > For UNION/EXCEPT/INTERSECT queries where you're dumping the contents > into a table via INTO, you need to specify all result table modifiers in > the *first* SQL statement where the INTO resides. > |
Tue, Oct 11 2011 2:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jon,
<< So a second 'encrypted with' is ignored and is redundant? >> Correct. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Oct 15 2011 6:52 PM | Permanent Link |
JonD | Thanks,
JonD On 2011-10-11 2:19 PM, Tim Young [Elevate Software] wrote: > Jon, > > << So a second 'encrypted with' is ignored and is redundant? >> > > Correct. > |
This web page was last updated on Wednesday, May 15, 2024 at 08:40 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |