firebird-net-provider — All about development of the MS .Net provider

[Firebird-net-provider] [FB-Tracker] Created: (DNET-659) Implement DDEX Provider as VSIX

[André Z. (J. <tr...@fi...>]

Implement DDEX Provider as VSIX
-------------------------------

                 Key: DNET-659
                 URL: http://tracker.firebirdsql.org/browse/DNET-659
             Project: .NET Data provider
          Issue Type: Sub-task
          Components: DDEX Provider
         Environment: Windows 8, VS2012
            Reporter: André Ziegler
            Assignee: Jiri Cincura


To fix the issue, that the DDEX provider gets lost after updating an Visual Studio extension (http://tracker.firebirdsql.org/browse/DNET-581), implement/install the DDEX provider as VSPackage


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[Firebird-net-provider] [FB-Tracker] Created: (DNET-658) Can't generate database from Entity Framework schema

[Ludovic C. (JIRA) <tr...@fi...>]

Can't generate database from Entity Framework schema
----------------------------------------------------

                 Key: DNET-658
                 URL: http://tracker.firebirdsql.org/browse/DNET-658
             Project: .NET Data provider
          Issue Type: Bug
          Components: ADO.NET Provider
    Affects Versions: 4.9.0.0
         Environment: Win 8.1 x64 / VS 2015 Community / EF 6.1.3 / EF.Firebird 4.9.0.0
            Reporter: Ludovic C.
            Assignee: Jiri Cincura


Hi,

I've designed a simple schema in Entity Framework using the visual entity designer. 

When I try to "generate the database from model" from the entity schema,  i get this error : 

"A procedure imported by 'Microsoft.VisualBasic.Activities.Compiler.dll' could not be loaded.

Though, I can successfully import a database as a Model, I can't generate a database from a model.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-net-provider] Bind Firebird Query to a RDLC report in Visual Studio 2012

[Vincent <v....@fr...>]

Hello,

I try to print data from firebird database in a Visual Studio 2012 
winforms App.
I want to use the ReportViewer component.

I create a form with a ReportViewer and a DataGrid. When I run the 
solution, Data appears in the grid but nothing in the reportviewer.

I do theses steps =>

I create an XSD named "Bulletin" with a DataTable "BulletinPaie" and two 
fields.
After, I create an RDLC report (Bulletin.rdlc), and I add a new dataset 
Dataset1.
I link Dataset1 to Bulletin for the connection, and BulletinPaie for the 
datasource.

In a winform, I drop a reportViewer component and I link it to Bulletin.rdlc

On the form load event I write this code :

         private void ImpressionPreview_Load(object sender, EventArgs e)
         {

             Bulletin b = new Bulletin();  //bulletin is the XSD élement

             string strsql = "SELECT  NUMORDRE,  LIBELLE FROM 
profil_detail";

             FbCommand cmd = new FbCommand(strsql, 
mainForm.fbConnectionPaie);
             FbDataAdapter adapter = new FbDataAdapter(cmd);

             adapter.Fill(b, b.Tables[0].TableName);
             ReportDataSource rds = new ReportDataSource("BulletinPaie", 
b.Tables[0]);

             this.reportViewer1.LocalReport.DataSources.Clear();
             this.reportViewer1.LocalReport.DataSources.Add(rds);
             this.reportViewer1.LocalReport.Refresh();
             this.reportViewer1.Refresh();


             dataGridView1.DataSource = b.Tables[0];
         }

Thanks for your help,

Vincent.

[Firebird-net-provider] [FB-Tracker] Created: (DNET-657) Lots of exceptions by transaction destructor

[Alexander Muylaert-G. (JIRA) <tr...@fi...>]

Lots of exceptions by transaction destructor
--------------------------------------------

                 Key: DNET-657
                 URL: http://tracker.firebirdsql.org/browse/DNET-657
             Project: .NET Data provider
          Issue Type: Bug
          Components: ADO.NET Provider
    Affects Versions: 4.9.0.0
            Reporter: Alexander Muylaert-Gelein
            Assignee: Jiri Cincura
            Priority: Critical


FbTransaction doesn't dispose the internal GDSTransaction anymore.  
If you look at FbTransaction.Commit, you'll notice it calls UpdateTransaction.  This method just sets the _transaction to null.  The dispose of this internal transaction isn't being called.

The disadvantage of this is that I have a lot of unwanted errors being spawned inside the gc thread.  If you replace the code in fbtransaction by the following, it seems to work fine

		private void UpdateTransaction()
		{
			if (_connection != null && _connection.InnerConnection != null)
			{
				_connection.InnerConnection.TransactionUpdated();
			}

			_isUpdated = true;
			_connection = null;
            if (_transaction != null)
            {
                _transaction.Dispose();
                _transaction = null;
            }
        }


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-net-provider] FirebirdSql.Data.FirebirdClient.4.9.0.0 Upgrade Fails Solution Compile

[LtColRDSChauhan <rds...@gm...>]

Hi,

The following failed compile of a Solution when upgraded to
FirebirdSql.Data.FirebirdClient.4.9.0.0

ServiceOutputEventHandler
FbRemoteEventEventHandler

Please help.
Thanks and Regards,
Rajiv

[Firebird-net-provider] ADO.NET provider 4.9.0.0

[Jiří Č. <ji...@ci...>]

More info
http://blog.cincura.net/233539-ado-net-provider-4-9-0-0-for-firebird-is-ready/
.

-- 
Mgr. Jiří Činčura
Independent IT Specialist

[Firebird-net-provider] [FB-Tracker] Created: (DNET-656) Creating a FB Datasource connection freezes VIsual Studio and restarts it.

[Ludovic C. (JIRA) <tr...@fi...>]

Creating a FB Datasource connection freezes VIsual Studio and restarts it. 
---------------------------------------------------------------------------

                 Key: DNET-656
                 URL: http://tracker.firebirdsql.org/browse/DNET-656
             Project: .NET Data provider
          Issue Type: Bug
          Components: DDEX Provider
    Affects Versions: 4.8.1.0
         Environment: Windows 8.1 x64. Visual Studio 2015 community edition. Firebird 2.5.5. 
            Reporter: Ludovic C.
            Assignee: Jiri Cincura
         Attachments: Capture.JPG

Hi

I am having issues with the .NET provider for firebird in Visual Studio 2015.

What I did : 

Installed EntityFramework
Installed FirebirdSQL.Data.FirebirdClient
Installed EntityFramework.Firebird
Installed the Firebird DDEX

Then, the Firbird provider is successfully added to the list of providers available when I try to create a new ADO.NET Entity Connection.

If I choose it, than create new connection, I can successfully open the new connection wizard. 

Now, 3 things can happen : 

1. If I click TEST CONNECTION without even populating the fields, I get a "Connection Successful" message.
2. If I click on OK, without putting in any info, I get ""Unable to find the requested .NET Framework Data Provider. It may not be installed"
3. If it try to put info in any of the fields, I get an error and then VIsual Studio crashes and restarts.

Please help!

 UnhandledException
   at FirebirdSql.VisualStudio.DataTools.FbDataConnectionUIControl.SetProperty(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.OnTextChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ComboBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr hWnd, Message& m)
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.UserControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ComboBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(Form form)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Microsoft.Data.ConnectionUI.DataConnectionDialog.Show(DataConnectionDialog dialog, IWin32Window owner)
   at Microsoft.VisualStudio.Data.HostServices.Environment.ShowDialog(Form form)
   at Microsoft.VisualStudio.Data.Package.DataConnectionDialog.ShowDialog()
   at Microsoft.VisualStudio.Data.Package.DataConnectionDialog.ShowDialog(Boolean connect)
   at Microsoft.Data.Entity.Design.VisualStudio.ModelWizard.Engine.EntityDataConnectionDialog.ShowDialog()
   at Microsoft.Data.Entity.Design.VisualStudio.ModelWizard.Gui.WizardPageDbConfig.newDBConnectionButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(Form form)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.RunDialog(Form form)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Microsoft.WizardFramework.WizardForm.Start(IWin32Window parent)
   at Microsoft.WizardFramework.WizardForm.Start()
   at Microsoft.Data.Entity.Design.VisualStudio.ModelWizard.ModelObjectItemWizard.RunStarted(Object automationObject, Dictionary`2 replacementsDictionary, WizardRunKind runKind, Object[] customParams)
   at Microsoft.VisualStudio.TemplateWizard.Wizard.Execute(Object application, Int32 hwndOwner, Object[]& ContextParams, Object[]& CustomParams, wizardResult& retval)
   at Microsoft.VisualStudio.Shell.Interop.IVsProject.AddItem(UInt32 itemidLoc, VSADDITEMOPERATION dwAddItemOperation, String pszItemName, UInt32 cFilesToOpen, String[] rgpszFilesToOpen, IntPtr hwndDlgOwner, VSADDRESULT[] pResult)
   at Microsoft.VisualStudio.Web.Application.WAProject.AddItem(UInt32 itemidLoc, VSADDITEMOPERATION dwAddItemOperation, String pszItemName, UInt32 cFilesToOpen, String[] rgpszFilesToOpen, IntPtr hwndDlgOwner, VSADDRESULT[] pResult)
   at Microsoft.VisualStudio.Web.Application.WAProject.Microsoft.VisualStudio.Shell.Interop.IVsProject.AddItem(UInt32 itemidLoc, VSADDITEMOPERATION dwAddItemOperation, String pszItemName, UInt32 cFilesToOpen, String[] rgpszFilesToOpen, IntPtr hwndDlgOwner, VSADDRESULT[] pResult)
   at Microsoft.VisualStudio.Shell.Interop.IVsProject.AddItem(UInt32 itemidLoc, VSADDITEMOPERATION dwAddItemOperation, String pszItemName, UInt32 cFilesToOpen, String[] rgpszFilesToOpen, IntPtr hwndDlgOwner, VSADDRESULT[] pResult)
   at Microsoft.VisualStudio.Dialogs.SVsDialogService.AddNewItem(NewProjectDialog npd, VSNEWPROJECTDLGINFO dlgInfo)
   at Microsoft.VisualStudio.Dialogs.SVsDialogService.InvokeDialog(VSNEWPROJECTDLGINFO dlgInfo, String& bstrLocation)
   at Microsoft.VisualStudio.Shell.Interop.IVsAddProjectItemDlg.AddProjectItemDlg(UInt32 itemidLoc, Guid& rguidProject, IVsProject pProject, UInt32 grfAddFlags, String lpszExpand, String lpszSelect, String& pbstrLocation, String& pbstrFilter, Int32& pfDontShowAgain)
   at Microsoft.VisualStudio.Web.Application.WAProject.CmdAddNewItem(Object sender, EventArgs e)
   at Microsoft.VisualStudio.Shell.OleMenuCommand.Invoke(Object inArg, IntPtr outArg, OLECMDEXECOPT options)
   at Microsoft.VisualStudio.Shell.OleMenuCommandService.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& commandGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
   at Microsoft.VisualStudio.Web.Application.FlavoredProjectBase.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Web.Application.WAProject.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Web.Application.FlavoredProjectBase.Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.Internal.VisualStudio.PlatformUI.HierarchyUtilities.<>c__DisplayClass35_0.<ExecHierParentChain>b__1()
   at Microsoft.VisualStudio.ErrorHandler.CallWithCOMConvention(Func`1 method, Boolean reportError, Boolean setShellErrorInfo)
   at Microsoft.Internal.VisualStudio.PlatformUI.HierarchyUtilities.ExecHierParentChain(IVsHierarchyItemManager manager, IVsUIHierarchy lpUIHCmd, IVsUIHierarchy lpUIHCurrent, UInt32 itemidCurrent, Guid& pguidCmdGroupRef, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.PlatformUI.PivotNavigatorCommandTarget.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.PlatformUI.SolutionNavigatorCommandTarget.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Shell.WindowPane.Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& guidGroup, UInt32 nCmdId, UInt32 nCmdExcept, IntPtr pIn, IntPtr vOut)
   at Microsoft.VisualStudio.Platform.WindowManagement.DocumentObjectSite.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Shell.Interop.IVsUIDataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
   at Microsoft.Internal.VisualStudio.PlatformUI.DataSource.Invoke(String verb, Object pvaIn, Object& pvaOut)
   at Microsoft.VisualStudio.PlatformUI.VsCommand.Execute(Object parameter)
   at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at Microsoft.VisualStudio.PlatformUI.NativeMethods.DispatchMessage(MSG& lpmsg)
   at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.<>c.<PushMessageLoopOnContextMenuTrackingComponent>b__218_1(Object sender, PreTranslateMessageEventArgs args)
   at Microsoft.VisualStudio.PlatformUI.OleComponentSupport.OleComponent.FPreTranslateMessageCore(MSG[] pMsg)
   at Microsoft.VisualStudio.PlatformUI.OleComponentSupport.OleComponent.<>c__DisplayClass23_0.<Microsoft.VisualStudio.OLE.Interop.IOleComponent.FPreTranslateMessage>b__0()
   at Microsoft.VisualStudio.PlatformUI.OleComponentSupport.OleComponent.CallAndReturnOnException(Func`1 method, Int32 retValueOnException)
   at Microsoft.VisualStudio.PlatformUI.OleComponentSupport.OleComponent.Microsoft.VisualStudio.OLE.Interop.IOleComponent.FPreTranslateMessage(MSG[] pMsg)
   at Microsoft.VisualStudio.OLE.Interop.IOleComponentManager.FPushMessageLoop(UInt32 dwComponentID, UInt32 uReason, IntPtr pvLoopData)
   at Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService.PushMessageLoopOnContextMenuTrackingComponent()
   at Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Web.Application.WAProject.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Web.Application.FlavoredProjectBase.Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.Shell.Interop.IVsUIHierarchy.ExecCommand(UInt32 itemid, Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.Internal.VisualStudio.PlatformUI.HierarchyUtilities.<>c__DisplayClass35_0.<ExecHierParentChain>b__1()
   at Microsoft.VisualStudio.ErrorHandler.CallWithCOMConvention(Func`1 method, Boolean reportError, Boolean setShellErrorInfo)
   at Microsoft.Internal.VisualStudio.PlatformUI.HierarchyUtilities.ExecHierParentChain(IVsHierarchyItemManager manager, IVsUIHierarchy lpUIHCmd, IVsUIHierarchy lpUIHCurrent, UInt32 itemidCurrent, Guid& pguidCmdGroupRef, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
   at Microsoft.VisualStudio.PlatformUI.HierarchyItem.HierarchyContextMenuController.ShowContextMenu(IEnumerable`1 items, Point location)
   at Microsoft.Internal.VisualStudio.PlatformUI.ContextMenuController.ShowContextMenu(IEnumerable`1 items, Point location, Func`2 getController)
   at Microsoft.Internal.VisualStudio.PlatformUI.ContextMenuController.ShowContextMenu(IEnumerable`1 items, Point location)
   at Microsoft.Internal.VisualStudio.PlatformUI.PivotTreeView.OnContextMenuOpening(ContextMenuEventArgs e)
   at System.Windows.FrameworkElement.OnContextMenuOpeningThunk(Object sender, ContextMenuEventArgs e)
   at System.Windows.Controls.ContextMenuEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.ContentElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.ContentElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
   at System.Windows.Controls.PopupControlService.RaiseContextMenuOpeningEvent(IInputElement source, Double x, Double y, Boolean userInitiated)
   at System.Windows.Controls.PopupControlService.ProcessMouseUp(Object sender, MouseButtonEventArgs e)
   at System.Windows.Controls.PopupControlService.OnPostProcessInput(Object sender, ProcessInputEventArgs e)
   at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(ProcessInputEventHandler postProcessInput, ProcessInputEventArgs processInputEventArgs)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at DevExpress.DXCore.Threading.SynchronizationManager.IDENativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[Геннадий З. <zab...@gm...>]

Hm, I've already finished the implementation. I will rebase it and
prepare for merge.
And I'll remove WIP mark.

Looks like my bad, I was waiting for something.


On 17 December 2015 at 13:02, Jiří Činčura <ji...@ci...> wrote:
> The PR is marked as WIP…
>
> --
> Mgr. Jiří Činčura
> Independent IT Specialist
>
> On Thu, Dec 17, 2015, at 09:54, Геннадий Забула wrote:
>> And so it was.
>> I'm also don't understand why don't merge the PR.
>> People can start using .NET with FB 3.0 using legacy authentication
>> and new features like native boolean fields.
>>
>> On 16 December 2015 at 22:11, Mark Rotteveel <ma...@la...>
>> wrote:
>> > Support for Boolean does not require protocol version 13 support, and could
>> > be added without problems.
>> >
>> > Mark
>> >
>> >
>> > ----- Reply message -----
>> > Van: "Геннадий Забула" <zab...@gm...>
>> > Aan: "For users and developers of the Firebird .NET providers"
>> > <fir...@li...>
>> > Onderwerp: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean
>> > Datum: wo, dec. 16, 2015 20:38
>> >
>> > It is implemented in PR:
>> > https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/40
>> > But since there is no overall support for FB 3.0 (especially new
>> > authentication) the PR is suspended.
>> >
>> > On 16 December 2015 at 21:21, Rick Roen <ric...@gm...> wrote:
>> >> I'm pretty sure this is a known problem, but I get a message "invalid data
>> >> type" exception when I ExecuteDataReader against a FB3 table with a
>> >> boolean
>> >> field. I can provide the error stack if necessary.
>> >>
>> >> Is there an ETA date to get this working?
>> >>
>> >> Regards,
>> >> Rick
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >>
>> >> _______________________________________________
>> >> Firebird-net-provider mailing list
>> >> Fir...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>> >>
>> >
>> > ------------------------------------------------------------------------------
>> > _______________________________________________
>> > Firebird-net-provider mailing list
>> > Fir...@li...
>> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>> >
>> >
>> > ------------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Firebird-net-provider mailing list
>> > Fir...@li...
>> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>> >
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Firebird-net-provider mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[Jiří Č. <ji...@ci...>]

The PR is marked as WIP…

-- 
Mgr. Jiří Činčura
Independent IT Specialist

On Thu, Dec 17, 2015, at 09:54, Геннадий Забула wrote:
> And so it was.
> I'm also don't understand why don't merge the PR.
> People can start using .NET with FB 3.0 using legacy authentication
> and new features like native boolean fields.
> 
> On 16 December 2015 at 22:11, Mark Rotteveel <ma...@la...>
> wrote:
> > Support for Boolean does not require protocol version 13 support, and could
> > be added without problems.
> >
> > Mark
> >
> >
> > ----- Reply message -----
> > Van: "Геннадий Забула" <zab...@gm...>
> > Aan: "For users and developers of the Firebird .NET providers"
> > <fir...@li...>
> > Onderwerp: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean
> > Datum: wo, dec. 16, 2015 20:38
> >
> > It is implemented in PR:
> > https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/40
> > But since there is no overall support for FB 3.0 (especially new
> > authentication) the PR is suspended.
> >
> > On 16 December 2015 at 21:21, Rick Roen <ric...@gm...> wrote:
> >> I'm pretty sure this is a known problem, but I get a message "invalid data
> >> type" exception when I ExecuteDataReader against a FB3 table with a
> >> boolean
> >> field. I can provide the error stack if necessary.
> >>
> >> Is there an ETA date to get this working?
> >>
> >> Regards,
> >> Rick
> >>
> >>
> >> ------------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Firebird-net-provider mailing list
> >> Fir...@li...
> >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
> >>
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Firebird-net-provider mailing list
> > Fir...@li...
> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
> >
> >
> > ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Firebird-net-provider mailing list
> > Fir...@li...
> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
> >
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[Геннадий З. <zab...@gm...>]

And so it was.
I'm also don't understand why don't merge the PR.
People can start using .NET with FB 3.0 using legacy authentication
and new features like native boolean fields.

On 16 December 2015 at 22:11, Mark Rotteveel <ma...@la...> wrote:
> Support for Boolean does not require protocol version 13 support, and could
> be added without problems.
>
> Mark
>
>
> ----- Reply message -----
> Van: "Геннадий Забула" <zab...@gm...>
> Aan: "For users and developers of the Firebird .NET providers"
> <fir...@li...>
> Onderwerp: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean
> Datum: wo, dec. 16, 2015 20:38
>
> It is implemented in PR:
> https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/40
> But since there is no overall support for FB 3.0 (especially new
> authentication) the PR is suspended.
>
> On 16 December 2015 at 21:21, Rick Roen <ric...@gm...> wrote:
>> I'm pretty sure this is a known problem, but I get a message "invalid data
>> type" exception when I ExecuteDataReader against a FB3 table with a
>> boolean
>> field. I can provide the error stack if necessary.
>>
>> Is there an ETA date to get this working?
>>
>> Regards,
>> Rick
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Firebird-net-provider mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>

Re: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[M. R. <ma...@la...>]

Support for Boolean does not require protocol version 13 support, and could be added without problems.
Mark

----- Reply message -----
Van: "Геннадий Забула" <zab...@gm...>
Aan: "For users and developers of the Firebird .NET providers" <fir...@li...>
Onderwerp: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean
Datum: wo, dec. 16, 2015 20:38

It is implemented in PR:
https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/40
But since there is no overall support for FB 3.0 (especially new
authentication) the PR is suspended.

On 16 December 2015 at 21:21, Rick Roen <ric...@gm...> wrote:
> I'm pretty sure this is a known problem, but I get a message "invalid data
> type" exception when I ExecuteDataReader against a FB3 table with a boolean
> field. I can provide the error stack if necessary.
>
> Is there an ETA date to get this working?
>
> Regards,
> Rick
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>

------------------------------------------------------------------------------
_______________________________________________
Firebird-net-provider mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[Геннадий З. <zab...@gm...>]

It is implemented in PR:
https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/40
But since there is no overall support for FB 3.0 (especially new
authentication) the PR is suspended.

On 16 December 2015 at 21:21, Rick Roen <ric...@gm...> wrote:
> I'm pretty sure this is a known problem, but I get a message "invalid data
> type" exception when I ExecuteDataReader against a FB3 table with a boolean
> field. I can provide the error stack if necessary.
>
> Is there an ETA date to get this working?
>
> Regards,
> Rick
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>

[Firebird-net-provider] FB3/provider 4.9.0.0 Boolean

[Rick R. <ric...@gm...>]

I'm pretty sure this is a known problem, but I get a message "invalid data
type" exception when I ExecuteDataReader against a FB3 table with a boolean
field. I can provide the error stack if necessary.

Is there an ETA date to get this working?

Regards,
Rick

[Firebird-net-provider] Gds.NET 2.5.1 overview

[slucas <sl...@iq...>]

hello one and all,

i am working with version 2.5.1 of ADO.NET because i need to compile the 
simplest code for .NET 2 CF.  under the build of 2.5.1, i found a batch 
file \netcf\build.bat and i surmise that the Version10 cs files make fit 
my .NET2CF platform best.

so at this point, i was able to port and run the code for GdsConnection 
Connect and Disconnect and i believe successfully connected to a host IP 
server from my mobile device, which happens to be a motorola MT2090, via 
the wifi LAN.  i verified that IsConnected and ProtocolVersion and 
ProtocolArchitecture threw back sensible values.

ok, so now i am looking into GdsDatabase.cs file and i am confused. how 
do i connect to the database with user and passwd, start a single 
transaction, throw a select in and retrieve the field values, or throw 
in an insert, and then commit the transaction and close the database.  i 
want to do very basic stuff.

so i am asking for example/sample/tutorial code to show these basics but 
using the GdsConnection *.cs modules, Version10, and not the more modern 
FbConnection etc. code.

did that make sense?  thank you in advance, lucas

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Геннадий З. <zab...@gm...>]

The name '{name}' is longer than Firebird's {LengthLimit} characters
limit for objects names.

On 9 December 2015 at 15:42, Jiří Činčura <ji...@ci...> wrote:
> Be my guest:
> https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/commit/4d8d1b8a5d72b6304e8d15af36542f72a9b5da8c#diff-02c77ebea06976e32e7ce3b42bca24c9R641
> . I'm open to rewording it, as I'm bit flat on creativity today. :D
>
> --
> Mgr. Jiří Činčura
> Independent IT Specialist
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Jiří Č. <ji...@ci...>]

Be my guest:
https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/commit/4d8d1b8a5d72b6304e8d15af36542f72a9b5da8c#diff-02c77ebea06976e32e7ce3b42bca24c9R641
. I'm open to rewording it, as I'm bit flat on creativity today. :D

-- 
Mgr. Jiří Činčura
Independent IT Specialist

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Геннадий З. <zab...@gm...>]

I think it should be ArgumentOutOfRange

On 9 December 2015 at 15:13, Jiří Činčura <ji...@ci...> wrote:
> On Wed, Dec 9, 2015, at 13:43, Jiří Činčura wrote:
>> On Sun, Dec 6, 2015, at 18:29, Геннадий Забула wrote:
>> > I think the earlier it will be thrown the better. Also, in exception
>> > message you can include text or/and link about workaround of this FB
>> > limitation. It will be a good convenience for library users.
>>
>> As I don't have any opinion on that I'll go with you. :)
>
> ArgumentException or maybe ArgumentOutOfRange exception?
>
> --
> Mgr. Jiří Činčura
> Independent IT Specialist
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Jiří Č. <ji...@ci...>]

On Wed, Dec 9, 2015, at 13:43, Jiří Činčura wrote:
> On Sun, Dec 6, 2015, at 18:29, Геннадий Забула wrote:
> > I think the earlier it will be thrown the better. Also, in exception
> > message you can include text or/and link about workaround of this FB
> > limitation. It will be a good convenience for library users.
> 
> As I don't have any opinion on that I'll go with you. :)

ArgumentException or maybe ArgumentOutOfRange exception?

-- 
Mgr. Jiří Činčura
Independent IT Specialist

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Jiří Č. <ji...@ci...>]

On Sun, Dec 6, 2015, at 18:29, Геннадий Забула wrote:
> I think the earlier it will be thrown the better. Also, in exception
> message you can include text or/and link about workaround of this FB
> limitation. It will be a good convenience for library users.

As I don't have any opinion on that I'll go with you. :)

> Ctor of what?

Of the FbMigrationSqlGenerator.

-- 
Mgr. Jiří Činčura
Independent IT Specialist

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Jiří Č. <ji...@ci...>]

> Will this PR get merged:
> https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/43
> ?

Yes.

-- 
Mgr. Jiří Činčura
Independent IT Specialist

[Firebird-net-provider] [FB-Tracker] Reopened: (DNET-654) Trimming ten-thousandths of a second during TIMESPAN conversion to the DateTime in the NET Provider for Firebird.

[Jiri C. (JIRA) <tr...@fi...>]

     [ http://tracker.firebirdsql.org/browse/DNET-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiri Cincura reopened DNET-654:
-------------------------------


> Trimming ten-thousandths of a second during TIMESPAN conversion to the DateTime in the NET Provider for Firebird.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DNET-654
>                 URL: http://tracker.firebirdsql.org/browse/DNET-654
>             Project: .NET Data provider
>          Issue Type: Bug
>          Components: ADO.NET Provider
>    Affects Versions: 4.7.0.0
>         Environment: Windows 10, 64-bit
>            Reporter: Kamil Kocian
>            Assignee: Jiri Cincura
>             Fix For: vNext
>
>
> The NET Provider for Firebird trims ten-thousandths of a second during TIMESPAN conversion to the .NET DateTime type in method TypeDecoder.DecodeTime(int sql_time). Trimming the ten-thousandths of a second is causing problem when comparing time read from Firebird to .NET and using the value again in SQL statements. 
> However it is possible to initialize .NET type DateTime(or TimeSpan) with number of ticks, this way keeping the precision of Firebird TIMESTAMP in .NET. 
> Problematic source code in FirebirdSql.Data.FirebirdClient\Common\TypeDecoder.cs :
> public static TimeSpan DecodeTime(int sql_time)
> {
> 	int millisInDay = sql_time / 10;
> 	int hour = millisInDay / 3600000;
> 	int minute = (millisInDay - hour * 3600000) / 60000;
> 	int second = (millisInDay - hour * 3600000 - minute * 60000) / 1000;
> 	int millisecond = millisInDay - hour * 3600000 - minute * 60000 - second * 1000;
> 	return new TimeSpan(0, hour, minute, second, millisecond);
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Firebird-net-provider] [FB-Tracker] Created: (DNET-655) Ugly delayed exceptions (error reading data from the connection) on certain driver versions in VS2013 / all versions in VS2015

[Jimmy G. (JIRA) <tr...@fi...>]

Ugly delayed exceptions (error reading data from the connection) on certain driver versions in VS2013 / all versions in VS2015
------------------------------------------------------------------------------------------------------------------------------

                 Key: DNET-655
                 URL: http://tracker.firebirdsql.org/browse/DNET-655
             Project: .NET Data provider
          Issue Type: Bug
          Components: ADO.NET Provider, DDEX Provider, Entity Framework support
    Affects Versions: 4.8.1.0, 4.8.0.0, 4.7.0.0, 4.6.4.0, 4.6.3.0, 4.6.2.0, 4.6.1.0, 4.6.0.0
         Environment: Windows Server 2008 RS Standard Service Pack 1
IIS 7.5
Using Visual Studio 2013 the errors occur with version 4.6.0.0 + (version 4.5.1.0 is fine!!)
Using Visual Studio 2015 the errors occur with version 4.5.1.0 also !!
EntityFramework 6.0.0.0

            Reporter: Jimmy Gee
            Assignee: Jiri Cincura



I have isolated all my Firebird code into a single webservice module and are using very basic using() { } pattern to access the database.
The error happens sporadic after some time (if it happens) but is reproducable in the way that you can sort of guarantee that it will start happening after some hours max.
As soon as I use Visual Studio 2013 and driver version 4.5.1.0 or below it will NEVER happen (running for days and weeks)
As soon as I use Visual Studio 2013 and driver version 4.6.0.0 or above it WILL happen (after minutes or hours max.) It is very BAD as soon as it happens!!
As soon as I use Visual Studio 2015 (no matter which driver version) it WILL happen!!
.Net Framework version 4.5 4.51 4.52 4.6 does NOT matter!!

sample code:

using (var context = new VodmateEFCtx())
{
    return context.DOWNLOADS.SingleOfDefault(x => x.dlcode = "xxxxxx");
}



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Геннадий З. <zab...@gm...>]

One more question.
Will this PR get merged:
https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/pull/43
?

On 6 December 2015 at 19:29, Геннадий Забула <zab...@gm...> wrote:
>> Do you think it should throw exception? I would rather let that for
>> Firebird. Somebody might tweak the script or something like that.
>
>> I know you proposed hashing the name, but that's not reasonable general
>> solution. The database would look gibberish for outside view. Nobody
>> would know what's what.
>
> I think the earlier it will be thrown the better. Also, in exception
> message you can include text or/and link about workaround of this FB
> limitation. It will be a good convenience for library users.
>
> As for hashing, agree, when we implemented this solution I missed the
> possibility to specify custom short names for tables.
>
>> > 4. Also, I don't see where IFbMigrationSqlGeneratorBehavior can be
>> > injected from client's app code.
>> In ctor.
>
> Ctor of what?
>
>> Agree. I'd like to first see somebody outside implement other behavior.
>> Then we can talk about what to extract - i.e. the system tables logic
>> etc.
>
> In specified links, I've provided my implementation of generator-per-table.
>
>
> On 5 December 2015 at 17:54, Jiří Činčura <ji...@ci...> wrote:
>>> 1. readonly IFbMigrationSqlGeneratorBehavior _behavior;
>>> Is used only in migration operations DropColumn/AlterColumn, not used
>>> in AddColumn.
>>
>> The AddColumnOperation calls Generate method for ColumnModel and this
>> method handles the identity stuff. Or do you mean something else?
>>
>>> 2. We have additional implementation of Check in (0,1) for boolean
>>> fields like implemented in SsdlToSql.cs
>>
>> Good idea. Added. (Testing it as we speak.)
>>
>>> 3. CreateItemName function doesn't support names longer than 31
>>> character.
>>
>> Do you think it should throw exception? I would rather let that for
>> Firebird. Somebody might tweak the script or something like that.
>>
>> I know you proposed hashing the name, but that's not reasonable general
>> solution. The database would look gibberish for outside view. Nobody
>> would know what's what.
>>
>>> 4. Also, I don't see where IFbMigrationSqlGeneratorBehavior can be
>>> injected from client's app code.
>>
>> In ctor.
>>
>>> 5. I think the generator creation code in
>>> DefaultFbMigrationSqlGeneratorBehavior will be copied to a possible
>>> new implementation, so it is better to split logic. See base class:
>>
>> Agree. I'd like to first see somebody outside implement other behavior.
>> Then we can talk about what to extract - i.e. the system tables logic
>> etc.
>>
>> --
>> Mgr. Jiří Činčura
>> Independent IT Specialist
>>
>> ------------------------------------------------------------------------------
>> Go from Idea to Many App Stores Faster with Intel(R) XDK
>> Give your users amazing mobile app experiences with Intel(R) XDK.
>> Use one codebase in this all-in-one HTML5 development environment.
>> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
>> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>> _______________________________________________
>> Firebird-net-provider mailing list
>> Fir...@li...
>> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Re: [Firebird-net-provider] 4.9.0 beta 1 release

[Геннадий З. <zab...@gm...>]

> Do you think it should throw exception? I would rather let that for
> Firebird. Somebody might tweak the script or something like that.

> I know you proposed hashing the name, but that's not reasonable general
> solution. The database would look gibberish for outside view. Nobody
> would know what's what.

I think the earlier it will be thrown the better. Also, in exception
message you can include text or/and link about workaround of this FB
limitation. It will be a good convenience for library users.

As for hashing, agree, when we implemented this solution I missed the
possibility to specify custom short names for tables.

> > 4. Also, I don't see where IFbMigrationSqlGeneratorBehavior can be
> > injected from client's app code.
> In ctor.

Ctor of what?

> Agree. I'd like to first see somebody outside implement other behavior.
> Then we can talk about what to extract - i.e. the system tables logic
> etc.

In specified links, I've provided my implementation of generator-per-table.


On 5 December 2015 at 17:54, Jiří Činčura <ji...@ci...> wrote:
>> 1. readonly IFbMigrationSqlGeneratorBehavior _behavior;
>> Is used only in migration operations DropColumn/AlterColumn, not used
>> in AddColumn.
>
> The AddColumnOperation calls Generate method for ColumnModel and this
> method handles the identity stuff. Or do you mean something else?
>
>> 2. We have additional implementation of Check in (0,1) for boolean
>> fields like implemented in SsdlToSql.cs
>
> Good idea. Added. (Testing it as we speak.)
>
>> 3. CreateItemName function doesn't support names longer than 31
>> character.
>
> Do you think it should throw exception? I would rather let that for
> Firebird. Somebody might tweak the script or something like that.
>
> I know you proposed hashing the name, but that's not reasonable general
> solution. The database would look gibberish for outside view. Nobody
> would know what's what.
>
>> 4. Also, I don't see where IFbMigrationSqlGeneratorBehavior can be
>> injected from client's app code.
>
> In ctor.
>
>> 5. I think the generator creation code in
>> DefaultFbMigrationSqlGeneratorBehavior will be copied to a possible
>> new implementation, so it is better to split logic. See base class:
>
> Agree. I'd like to first see somebody outside implement other behavior.
> Then we can talk about what to extract - i.e. the system tables logic
> etc.
>
> --
> Mgr. Jiří Činčura
> Independent IT Specialist
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Firebird-net-provider mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

[Firebird-net-provider] Removing BDP

[Jiří Č. <ji...@ci...>]

Hi *,

anybody feeling sad for dropping BDP (if you know what that is)? I don't
think it makes sense keep dead technology there. It will still be in
Git's history, if needed.

-- 
Mgr. Jiří Činčura
Independent IT Specialist