SQL Anywhere database - Re: Proxy tables trimming

Author

Re: Proxy tables trimming - EBF availability

Pavel

2005-10-31, 9:23 am

Greetings and thanks. When will this EBF be available?
Pavel

> Problem fixed. Fix will appear in EBF 3214 for ASA 9.0.2.
>
> --
> Joshua Savill
> iAnywhere Solutions - Product Support Analyst
>
> "Joshua Savill" <jsavill@ianywhere.com> wrote in message
> news:4360de98$1@foru
ms-1-dub...
> news:4jk1m15fa2gknf8
tskeqkjqsgvff0tff0q@
4ax.com... >> It
> is a bug, probably introduced sometime in version 8. I
> have posted >> a reproducible below.
> ASA 8 and 9, but >> not in 7:
> ;DBN=ddd2'; >>
> IDENTIFIED BY 'sql'; >>
> make >>>up with something... any suggestions?
> if >>>yes, will it be fixed in some EBF or next release?
> If it's >>>not a bug, why IS that trimming THERE?
> when >>>> the proxy table is in a JOIN with the local
> table. >>>>
> databases >>>> created with all the default settings. The
> table t is >>>> identical in both databases, and the
> proxy_t was defined >>>> as shown in an earlier posting.
> proxy_t; >>>> END;
> Sybase >>>> >Central for both databases, they are both set
> to "No". >>>> But I >didn't know about this feature, so
> for me from now >>>> on, this >is a good thing to
> remember. Thanks, Rudy! >>>> >
> the >>>> >columns in proxy tables contain whitespaces (=
> columns >>>> are >not trimmed) perfectly like in original
> tables. >>>> >
> database >>>> >
> the >>>> >following:
> the >>>> >opposite. There is still a possibility that I'm
> missing >>>> >something important, but this "thing" is
> beyond my >>>> knowledge >opportunities, so I need
> external advices, >>>> please. >
> proxy_t; >>>> >> pkey,STRING('[',proxy_t.name,']')
> ;ENG=ddd2 >>>> >> ;DBN=ddd2';
> proxy_t; >>>> >>
> Suddenly >>>> >> trimming spaces would be a *huge* problem
> , and there >>>> have >> been no other reports I am aware
> of. >>>> >>
> 9.0.2.2551 >>>> >> I've >come accross this:
> trims >>>> >> >values!!!
> in >>>> the >> >remote database, the column value is
> "Joseph " >>>> but >> when >you create an so called
> existing table (proxy >>>> table) >> in >local database,
> the value of that column >>>> will be >> "Joseph". >
> they >>>> >> differ. >Am I missing something? Could
> somebody please >>>> >> explain it? >
> SQL Anywhere and MobiLink Professional >>>> Services >>
> www.risingroad.com >>>>
> groad-20 >>>> bcarter@risingroad.com
> Services >>>> www.risingroad.com
>
http://www.amazon.com/exec/obidos/A...7/risingroad-20
> Services >> www.risingroad.com
>
>

Joshua Savill

2005-10-31, 11:23 am

There is no set time when this EBF will be released. Once the EBF has passed
QA testing it will be published for download. On average it takes 2-3 weeks
for an EBF to pass through QA.

--
Joshua Savill
iAnywhere Solutions - Product Support Analyst

<Pavel> wrote in message news:436619d1.542c.1681692777@sybase.com...[color=darkred]
> Greetings and thanks. When will this EBF be available?
> Pavel
>
> http://www.amazon.com/exec/obidos/A...7/risingroad-20

Pavel

2005-10-31, 1:23 pm

Thanks for the info...
Pavel

> There is no set time when this EBF will be released. Once
> the EBF has passed QA testing it will be published for
> download. On average it takes 2-3 weeks for an EBF to
> pass through QA.
>
> --
> Joshua Savill
> iAnywhere Solutions - Product Support Analyst
>
>
> <Pavel> wrote in message
> 9.0.2. >>
> message >> news:4360de98$1@foru
ms-1-dub...
> problem >> > to engineering for review.
> It >> is a bug, probably introduced sometime in version 8.
> I >> have posted >> a reproducible below.
> in >> ASA 8 and 9, but >> not in 7:
> ;ENG=ddd2 >> ;DBN=ddd2'; >>
> or >> make >>>up with something... any suggestions?
> and >> if >>>yes, will it be fixed in some EBF or next
> release? >> If it's >>>not a bug, why IS that trimming
> THERE? >> >>>
> The >> table t is >>>> identical in both databases, and
> the >> proxy_t was defined >>>> as shown in an earlier
> posting. >> >>>>
> loc >> >>>> JOIN proxy_t AS rem ON loc.pkey=rem.pkey
> set >> to "No". >>>> But I >didn't know about this feature
> , so >> for me from now >>>> on, this >is a good thing to
> tables. >> >>>> >Regarding what you've written, I've
> realized that >> the >>>> >columns in proxy tables contain
> whitespaces (= >> columns >>>> are >not trimmed) perfectly
> like in original >> tables. >>>> >
> your >> >>>> example >of the following:
> run >> the >>>> >following:
> be >> the >>>> >opposite. There is still a possibility
> that I'm >> missing >>>> >something important, but this
> "thing" is >> beyond my >>>> knowledge >opportunities, so
> I need >> external advices, >>>> please. >
> 9.0.2.3193 >> >>>> >> databases:
> DBA >> >>>> >> IDENTIFIED BY 'sql';
> 'target..DBA.t'; >> >>>> >>
> problem >> , and there >>>> have >> been no other reports
> I am aware >> of. >>>> >>
> example: >> in >>>> the >> >remote database, the column
> value is >> "Joseph " >>>> but >> when >you create an
> so called >> existing table (proxy >>>> table) >> in
> values, because >> they >>>> >> differ. >Am I missing
> something? Could >> somebody please >>>> >> explain it? >
> RisingRoad >> SQL Anywhere and MobiLink Professional >>>>
> Services >> >> www.risingroad.com >>>>
> SQL Anywhere and MobiLink Professional >> Services >>>>
> www.risingroad.com >> >>
>
http://www.amazon.com/exec/obidos/A...7/risingroad-20
>
>

Sponsored Links