Re: RunScript issue when run a utf-8 script.

[Noel Grandin]

Thanks, this bug has been fixed in SVN.

On 2012-10-25 04:56, 杨杰 wrote:
> Hi everyone,
> I run the RunScript tool with a utf-8 script. The script is saved by
> utf-8 encoding, and has a BOM of "EF BB BF" as the first 3 bytes of
> the file.
> And the parser cann't get a right sql for the Satement to execute.
> Then I saved the script by utf-8 without BOM, then it works!
> I think it's a robust issue for the tool.
>

[Thomas Mueller]

Hi,

I'm not sure if this is a 'bug', it's just that this wasn't supported. BOMs are supported for CSV files only so far, because the CSV files might be created in another application.

I would like to better understand the use case. Why do you have a BOM in the script file? How was the script file created?

Regards,

Thomas

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.

To post to this group, send email to h2-da...@googlegroups.com.
To unsubscribe from this group, send email to h2-database+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.

[杨杰]

Hi,

   Sorry to response so late! I can't access google groups normally because of the GFW!

   I export insert sqls from my Oracle database, using PL/SQL Developer. The default encoding

   is utf-8 with bom.

在 2012年10月26日星期五UTC+8上午1时17分11秒，Thomas Mueller写道：

Hi,

I'm not sure if this is a 'bug', it's just that this wasn't supported. BOMs are supported for CSV files only so far, because the CSV files might be created in another application.

I would like to better understand the use case. Why do you have a BOM in the script file? How was the script file created?

Regards,

Thomas

On Thu, Oct 25, 2012 at 9:11 AM, Noel Grandin <noelg...@gmail.com> wrote:

Thanks, this bug has been fixed in SVN.

On 2012-10-25 04:56, 杨杰 wrote:

Hi everyone,
I run the RunScript tool with a utf-8 script. The script is saved by utf-8 encoding, and has a BOM of "EF BB BF" as the first 3 bytes of the file.
And the parser cann't get a right sql for the Satement to execute.
Then I saved the  script by utf-8 without BOM, then it works!
I think it's a robust issue for the tool.

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.

To post to this group, send email to h2-da...@googlegroups.com.

To unsubscribe from this group, send email to h2-database...@googlegroups.com.

[杨杰]

Hi,

   Sorry to response so late! I can't access google groups normally because of the GFW!

   I export insert sqls from my Oracle database, using PL/SQL Developer. The default encoding

   is utf-8 with bom.

在 2012年10月26日星期五UTC+8上午1时17分11秒，Thomas Mueller写道：

Hi,

I'm not sure if this is a 'bug', it's just that this wasn't supported. BOMs are supported for CSV files only so far, because the CSV files might be created in another application.

I would like to better understand the use case. Why do you have a BOM in the script file? How was the script file created?

Regards,

Thomas

On Thu, Oct 25, 2012 at 9:11 AM, Noel Grandin <noelg...@gmail.com> wrote:

Thanks, this bug has been fixed in SVN.

On 2012-10-25 04:56, 杨杰 wrote:

Hi everyone,
I run the RunScript tool with a utf-8 script. The script is saved by utf-8 encoding, and has a BOM of "EF BB BF" as the first 3 bytes of the file.
And the parser cann't get a right sql for the Satement to execute.
Then I saved the  script by utf-8 without BOM, then it works!
I think it's a robust issue for the tool.

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.

To post to this group, send email to h2-da...@googlegroups.com.

To unsubscribe from this group, send email to h2-database...@googlegroups.com.